From: Christoph Hellwig <hch@infradead.org>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-btrfs@vger.kernel.org, Qu Wenruo <wqu@suse.com>,
Christoph Hellwig <hch@infradead.org>,
djwong@kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] iomap: add IOMAP_DIO_FSBLOCK_ALIGNED flag
Date: Wed, 22 Oct 2025 00:23:00 -0700 [thread overview]
Message-ID: <aPiGVJTpM8aohQpk@infradead.org> (raw)
In-Reply-To: <20251021-leber-dienlich-0bee81a049e1@brauner>
On Tue, Oct 21, 2025 at 03:03:08PM +0200, Christian Brauner wrote:
> On Mon, 13 Oct 2025 19:35:16 +1030, Qu Wenruo wrote:
> > Btrfs requires all of its bios to be fs block aligned, normally it's
> > totally fine but with the incoming block size larger than page size
> > (bs > ps) support, the requirement is no longer met for direct IOs.
> >
> > Because iomap_dio_bio_iter() calls bio_iov_iter_get_pages(), only
> > requiring alignment to be bdev_logical_block_size().
> >
> > [...]
>
> Applied to the vfs-6.19.iomap branch of the vfs/vfs.git tree.
> Patches in the vfs-6.19.iomap branch should appear in linux-next soon.
I'm not seeing it yet.
next prev parent reply other threads:[~2025-10-22 7:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 9:05 [PATCH v2] iomap: add IOMAP_DIO_FSBLOCK_ALIGNED flag Qu Wenruo
2025-10-13 11:14 ` Johannes Thumshirn
2025-10-13 20:39 ` Qu Wenruo
2025-10-14 4:36 ` Christoph Hellwig
2025-10-14 4:55 ` Qu Wenruo
2025-10-14 4:58 ` Christoph Hellwig
2025-10-14 5:10 ` Qu Wenruo
2025-10-16 12:10 ` Pankaj Raghav (Samsung)
2025-10-21 13:03 ` Christian Brauner
2025-10-22 7:23 ` Christoph Hellwig [this message]
2025-10-29 12:45 ` Christian Brauner
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=aPiGVJTpM8aohQpk@infradead.org \
--to=hch@infradead.org \
--cc=brauner@kernel.org \
--cc=djwong@kernel.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;
as well as URLs for NNTP newsgroup(s).