[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240611120626.513952-1-mjguzik@gmail.com>
Date: Tue, 11 Jun 2024 14:06:22 +0200
From: Mateusz Guzik <mjguzik@...il.com>
To: brauner@...nel.org
Cc: viro@...iv.linux.org.uk,
jack@...e.cz,
linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org,
linux-bcachefs@...r.kernel.org,
kent.overstreet@...ux.dev,
linux-xfs@...r.kernel.org,
david@...morbit.com,
Mateusz Guzik <mjguzik@...il.com>
Subject: [PATCH v2 0/4] inode_init_always zeroing i_state
As requested by Jan this is a 4-part series.
I diffed this against fs-next + my inode hash patch v3 as it adds one
i_state = 0 case. Should that hash thing not be accepted this bit is
trivially droppable from the patch.
Mateusz Guzik (4):
xfs: preserve i_state around inode_init_always in xfs_reinit_inode
vfs: partially sanitize i_state zeroing on inode creation
xfs: remove now spurious i_state initialization in xfs_inode_alloc
bcachefs: remove now spurious i_state initialization
fs/bcachefs/fs.c | 1 -
fs/inode.c | 13 +++----------
fs/xfs/xfs_icache.c | 5 +++--
3 files changed, 6 insertions(+), 13 deletions(-)
--
2.43.0
Powered by blists - more mailing lists