From: Christoph Hellwig <hch@infradead.org>
To: Keith Busch <kbusch@meta.com>
Cc: 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,
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: Re: [PATCHv2 2/5] block: report direct io attributes through file_getattr
Date: Mon, 13 Jul 2026 04:57:01 -0700 [thread overview]
Message-ID: <alTSjR-3gauVdr_6@infradead.org> (raw)
In-Reply-To: <20260710210646.3576365-3-kbusch@meta.com>
> #include "internal.h"
>
> @@ -88,13 +89,16 @@ int vfs_fileattr_get(struct dentry *dentry, struct file_kattr *fa)
> struct inode *inode = d_inode(dentry);
> int error;
>
> - if (!inode->i_op->fileattr_get)
> + if (!inode->i_op->fileattr_get && !S_ISBLK(inode->i_mode))
> return -ENOIOCTLCMD;
>
> error = security_inode_file_getattr(dentry, fa);
> if (error)
> return error;
>
> + if (!inode->i_op->fileattr_get)
> + return bdev_fileattr(inode, fa);
> +
> return inode->i_op->fileattr_get(dentry, fa);
While this is correct, it reads a bit odd as the check above
required the S_ISBLK above. I'd be tempted to move the
-ENOIOCTLCMD below the seurity check to mae it more obvious:
error = security_inode_file_getattr(dentry, fa);
if (error)
return error;
if (!inode->i_op->fileattr_get) {
if (!S_ISBLK(inode->i_mode))
return -ENOIOCTLCMD;
return bdev_fileattr(inode, fa);
}
...
next prev parent reply other threads:[~2026-07-13 11:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 21:06 [PATCHv2 0/5] direct-io file extended attributes Keith Busch
2026-07-10 21:06 ` [PATCHv2 1/5] fs: add direct io attributes to file_getattr Keith Busch
2026-07-13 10:14 ` Christoph Hellwig
2026-07-10 21:06 ` [PATCHv2 2/5] block: report direct io attributes through file_getattr Keith Busch
2026-07-13 11:57 ` Christoph Hellwig [this message]
2026-07-10 21:06 ` [PATCHv2 3/5] xfs: " Keith Busch
2026-07-13 12:00 ` Christoph Hellwig
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=alTSjR-3gauVdr_6@infradead.org \
--to=hch@infradead.org \
--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=kbusch@meta.com \
--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