Received-SPF: pass (google.com: domain of linux-kernel+bounces-209827-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
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,
	linux-bcachefs@vger.kernel.org,
	kent.overstreet@linux.dev,
	linux-xfs@vger.kernel.org,
	david@fromorbit.com,
	Mateusz Guzik <mjguzik@gmail.com>
Subject: [PATCH v2 0/4] inode_init_always zeroing i_state
Date: Tue, 11 Jun 2024 14:06:22 +0200
Message-ID: <20240611120626.513952-1-mjguzik@gmail.com>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

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