Thread (104 messages) 104 messages, 9 authors, 2024-06-17

Re: [PATCH 05/26] loop: regularize upgrading the lock size for direct I/O

From: Christoph Hellwig <hch@lst.de>
Date: 2024-06-11 05:59:13
Also in: ceph-devel, dm-devel, linux-bcache, linux-block, linux-m68k, linux-mmc, linux-nvme, linux-raid, linux-s390, linux-scsi, linux-um, nvdimm, virtualization, xen-devel

On Tue, Jun 11, 2024 at 02:56:59PM +0900, Damien Le Moal wrote:
quoted
+	if (!bsize)
+		bsize = loop_default_blocksize(lo, inode->i_sb->s_bdev);
If bsize is specified and there is a backing dev used with direct IO, should it
be checked that bsize is a multiple of bdev_logical_block_size(backing_bdev) ?
For direct I/O that check would be useful.  For buffered I/O we can do
read-modify-write cycles.  However this series is already huge and not
primarily about improving the loop driver parameter validation, so
I'll defer this for now.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help