From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH v3] iomap: follow the alignment requirement for iomap_dio_hole_iter()
Date: Tue, 4 Aug 2026 06:01:34 -0700 [thread overview]
Message-ID: <anHirnemstkJksXp@infradead.org> (raw)
In-Reply-To: <596ee3b5d0d23c42eefac651d24fae914fa16312.1785534430.git.wqu@suse.com>
On Sat, Aug 01, 2026 at 07:17:26AM +0930, Qu Wenruo wrote:
> +++ b/fs/iomap/direct-io.c
> @@ -409,7 +409,10 @@ static inline unsigned int iomap_dio_alignment(struct inode *inode,
> {
> if (dio_flags & IOMAP_DIO_FSBLOCK_ALIGNED)
> return i_blocksize(inode);
> - return bdev_logical_block_size(bdev);
> + /* @bdev can be NULL for hole cases. */
> + if (bdev)
> + return bdev_logical_block_size(bdev);
> + return SECTOR_SIZE;
No. As said for previous versions you should not use
iomap_dio_alignment. There is no such things as sub-fsblock alignment
for holes. All mappings need to be aligned on fs blocks, you can do
sub-mapping granularity I/O in it, but not align on it. So don't
call iomap_dio_alignment, but instead align down the shortened range
from the fault to a fs block boundary.
And really sort out the btrfs locking that we can't get rid of this
premature faulting as it keeps messing up core code way too much.
next prev parent reply other threads:[~2026-08-04 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 21:47 [PATCH v3] iomap: follow the alignment requirement for iomap_dio_hole_iter() Qu Wenruo
2026-08-04 13:01 ` Christoph Hellwig [this message]
2026-08-04 21:31 ` Qu Wenruo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=anHirnemstkJksXp@infradead.org \
--to=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=wqu@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox