From: Keith Busch <kbusch@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <kbusch@meta.com>,
linux-block@vger.kernel.org, shinichiro.kawasaki@wdc.com
Subject: Re: [PATCH blktests] create a test for direct io offsets
Date: Mon, 17 Nov 2025 14:53:49 -0700 [thread overview]
Message-ID: <aRuZbTBUNu8oTbty@kbusch-mbp> (raw)
In-Reply-To: <aPhhpohu8mc95oLp@infradead.org>
On Tue, Oct 21, 2025 at 09:46:30PM -0700, Christoph Hellwig wrote:
> On Tue, Oct 21, 2025 at 03:22:08PM -0600, Keith Busch wrote:
> > On Mon, Oct 20, 2025 at 10:28:09PM -0700, Christoph Hellwig wrote:
> > > seems like a huge win. Any chance you could try to get this done ASAP
> > > so that we could make the interface fully discoverable before 6.18 is
> > > released?
> >
> > I just want to make sure I am aligned to what you have in mind. Is this
> > something like this what you're looking for? This reports the kernel's
> > ability to handle a dio with memory that is discontiguous for a single
> > device "sector", and reports the virtual gap requirements.
>
> So, I think Christian really did not want more random stuff in statx,
> which would lead to using fsxattr instead.
I haven't forgotten about this. I was hoping I would make sense of the
request. It looks like only xfs makes use of fsxattr (it's the only one
that calls copy_fsxattr_to_user()). Is the intention that every
filesystem needs to implement support for fsxattr then?
next prev parent reply other threads:[~2025-11-17 21:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 20:54 [PATCH blktests] create a test for direct io offsets Keith Busch
2025-10-14 21:21 ` Bart Van Assche
2025-10-14 21:59 ` Keith Busch
2025-10-17 11:13 ` Christoph Hellwig
2025-10-20 16:20 ` Keith Busch
2025-10-21 5:28 ` Christoph Hellwig
2025-10-21 21:22 ` Keith Busch
2025-10-22 4:46 ` Christoph Hellwig
2025-11-17 21:53 ` Keith Busch [this message]
2025-11-18 5:54 ` Christoph Hellwig
2025-10-20 12:40 ` Shinichiro Kawasaki
2025-10-20 21:03 ` Keith Busch
2025-10-21 1:32 ` Shinichiro Kawasaki
2025-10-20 23:25 ` Chaitanya Kulkarni
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=aRuZbTBUNu8oTbty@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=hch@infradead.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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