Re: [PATCH v6 0/4] hide ->i_state behind accessors

[Christian Brauner <brauner@kernel.org>]

On Tue, 23 Sep 2025 12:47:06 +0200, Mateusz Guzik wrote:
> First commit message quoted verbatim with rationable + API:
> 
> [quote]
> Open-coded accesses prevent asserting they are done correctly. One
> obvious aspect is locking, but significantly more can checked. For
> example it can be detected when the code is clearing flags which are
> already missing, or is setting flags when it is illegal (e.g., I_FREEING
> when ->i_count > 0).
> 
> [...]

Applied to the vfs-6.19.inode branch of the vfs/vfs.git tree.
Patches in the vfs-6.19.inode branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.19.inode

[1/4] fs: provide accessors for ->i_state
      https://git.kernel.org/vfs/vfs/c/e9d1a9abd054
[2/4] Convert the kernel to use ->i_state accessors
      https://git.kernel.org/vfs/vfs/c/67d2f3e3d033
[3/4] Manual conversion of ->i_state uses
      https://git.kernel.org/vfs/vfs/c/b8173a2f1a0a
[4/4] fs: make plain ->i_state access fail to compile
      https://git.kernel.org/vfs/vfs/c/3c2b8d921da8