From: Mateusz Guzik <mjguzik@gmail.com>
To: brauner@kernel.org
Cc: viro@zeniv.linux.org.uk, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
josef@toxicpanda.com, kernel-team@fb.com, amir73il@gmail.com,
linux-btrfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-xfs@vger.kernel.org, ceph-devel@vger.kernel.org,
linux-unionfs@vger.kernel.org, Mateusz Guzik <mjguzik@gmail.com>
Subject: [PATCH v5 4/4] fs: make plain ->i_state access fail to compile
Date: Fri, 19 Sep 2025 17:49:04 +0200 [thread overview]
Message-ID: <20250919154905.2592318-5-mjguzik@gmail.com> (raw)
In-Reply-To: <20250919154905.2592318-1-mjguzik@gmail.com>
... to make sure all accesses are properly validated.
Merely renaming the var to __i_state still lets the compiler make the
following suggestion:
error: 'struct inode' has no member named 'i_state'; did you mean '__i_state'?
Unfortunately some people will add the __'s and call it a day.
In order to make it harder to mess up in this way, hide it behind a
struct. The resulting error message should be convincing in terms of
checking what to do:
error: invalid operands to binary & (have 'struct inode_state_flags' and 'int')
Of course people determined to do a plain access can still do it, but
nothing can be done for that case.
Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
---
include/linux/fs.h | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/include/linux/fs.h b/include/linux/fs.h
index 4ba2b274588a..3d678cd02fea 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -782,6 +782,13 @@ enum inode_state_flags_enum {
#define I_DIRTY (I_DIRTY_INODE | I_DIRTY_PAGES)
#define I_DIRTY_ALL (I_DIRTY | I_DIRTY_TIME)
+/*
+ * Use inode_state_read() & friends to access.
+ */
+struct inode_state_flags {
+ enum inode_state_flags_enum __state;
+};
+
/*
* Keep mostly read-only and often accessed (especially for
* the RCU path lookup and 'stat' data) fields at the beginning
@@ -840,7 +847,7 @@ struct inode {
#endif
/* Misc */
- enum inode_state_flags_enum i_state;
+ struct inode_state_flags i_state;
/* 32-bit hole */
struct rw_semaphore i_rwsem;
@@ -906,26 +913,26 @@ struct inode {
*/
static inline enum inode_state_flags_enum inode_state_read(struct inode *inode)
{
- return READ_ONCE(inode->i_state);
+ return READ_ONCE(inode->i_state.__state);
}
static inline void inode_state_add(struct inode *inode,
enum inode_state_flags_enum addflags)
{
- WRITE_ONCE(inode->i_state, inode->i_state | addflags);
+ WRITE_ONCE(inode->i_state.__state, inode->i_state.__state | addflags);
}
static inline void inode_state_del(struct inode *inode,
enum inode_state_flags_enum delflags)
{
- WRITE_ONCE(inode->i_state, inode->i_state & ~delflags);
+ WRITE_ONCE(inode->i_state.__state, inode->i_state.__state & ~delflags);
}
static inline void inode_state_set(struct inode *inode,
enum inode_state_flags_enum setflags)
{
- WRITE_ONCE(inode->i_state, setflags);
+ WRITE_ONCE(inode->i_state.__state, setflags);
}
static inline void inode_set_cached_link(struct inode *inode, char *link, int linklen)
--
2.43.0
next prev parent reply other threads:[~2025-09-19 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 15:49 [PATCH v5 0/4] hide ->i_state behind accessors Mateusz Guzik
2025-09-19 15:49 ` [PATCH v5 1/4] fs: provide accessors for ->i_state Mateusz Guzik
2025-09-19 15:49 ` [PATCH v5 2/4] Convert the kernel to use ->i_state accessors Mateusz Guzik
2025-09-19 15:49 ` [PATCH v5 3/4] Manual conversion of ->i_state uses Mateusz Guzik
2025-09-22 11:31 ` Jan Kara
2025-09-22 11:41 ` Mateusz Guzik
2025-09-19 15:49 ` Mateusz Guzik [this message]
2025-09-20 4:31 ` [PATCH v5 0/4] hide ->i_state behind accessors Russell Haley
2025-09-20 5:47 ` Mateusz Guzik
2025-09-22 11:36 ` Jan Kara
2025-09-22 11:40 ` Mateusz Guzik
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=20250919154905.2592318-5-mjguzik@gmail.com \
--to=mjguzik@gmail.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).