From: Keith Busch <kbusch@meta.com>
To: <linux-block@vger.kernel.org>, <linux-ext4@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>,
<linux-fsdevel@vger.kernel.org>, <linux-xfs@vger.kernel.org>
Cc: <axboe@kernel.dk>, <jack@suse.cz>, <brauner@kernel.org>,
<cem@kernel.org>, <jaegeuk@kernel.org>, <aalbersh@kernel.org>,
<tytso@mit.edu>, Keith Busch <kbusch@kernel.org>
Subject: [PATCHv2 0/5] direct-io file extended attributes
Date: Fri, 10 Jul 2026 14:06:41 -0700 [thread overview]
Message-ID: <20260710210646.3576365-1-kbusch@meta.com> (raw)
From: Keith Busch <kbusch@kernel.org>
The attributes reported through statx are incomplete for applications to
fully know exactly how IO construction is valid or not. The statx call
can report minimum memory alignment and total granularity, but it
doesn't show the underlying gap boundary requirements or max segments
per granule.
This series adds the minimum to the extended file attributes through
file_getattr. I hear this is the preferred interface for reporting such
things over adding more fields to statx. In order to get everything
under a single syscall, some of the attributes are duplicated from
statx.
Keith Busch (5):
fs: add direct io attributes to file_getattr
block: report direct io attributes through file_getattr
xfs: report direct io attributes through file_getattr
ext4: report direct io attributes through file_getattr
f2fs: report direct io attributes through file_getattr
block/bdev.c | 37 +++++++++++++++++++++++++++++++++++++
fs/ext4/ioctl.c | 23 +++++++++++++++++++++++
fs/f2fs/file.c | 20 ++++++++++++++++++++
fs/file_attr.c | 13 ++++++++++++-
fs/xfs/xfs_ioctl.c | 26 ++++++++++++++++++++++++++
include/linux/blkdev.h | 14 ++++++++++++++
include/linux/fileattr.h | 10 ++++++++--
include/uapi/linux/fs.h | 10 +++++++++-
8 files changed, 149 insertions(+), 4 deletions(-)
--
2.53.0-Meta
next reply other threads:[~2026-07-10 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 21:06 Keith Busch [this message]
2026-07-10 21:06 ` [PATCHv2 1/5] fs: add direct io attributes to file_getattr Keith Busch
2026-07-10 21:06 ` [PATCHv2 2/5] block: report direct io attributes through file_getattr Keith Busch
2026-07-10 21:06 ` [PATCHv2 3/5] xfs: " Keith Busch
2026-07-10 21:06 ` [PATCHv2 4/5] ext4: " Keith Busch
2026-07-10 21:06 ` [PATCHv2 5/5] f2fs: " Keith Busch
2026-07-10 21:53 ` [f2fs-dev] [PATCHv2 0/5] direct-io file extended attributes Eric Biggers
2026-07-10 22:58 ` Keith Busch
2026-07-11 0:24 ` Eric Biggers
2026-07-11 1:06 ` Keith Busch
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=20260710210646.3576365-1-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=aalbersh@kernel.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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