Re: [PATCH v2 4/4] bcachefs: remove now spurious i_state initialization

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Mateusz Guzik <mjguzik@xxxxxxxxx>
Subject: Re: [PATCH v2 4/4] bcachefs: remove now spurious i_state initialization
From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
Date: Tue, 11 Jun 2024 19:38:18 -0400
Cc: brauner@xxxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx, jack@xxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-bcachefs@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, david@xxxxxxxxxxxxx
In-reply-to: <20240611120626.513952-5-mjguzik@gmail.com>

On Tue, Jun 11, 2024 at 02:06:26PM GMT, Mateusz Guzik wrote:
> inode_init_always started setting the field to 0.
> 
> Signed-off-by: Mateusz Guzik <mjguzik@xxxxxxxxx>

Acked-by: Kent Overstreet <kent.overstreet@xxxxxxxxx>

References:
- [PATCH v2 0/4] inode_init_always zeroing i_state
  - From: Mateusz Guzik
- [PATCH v2 4/4] bcachefs: remove now spurious i_state initialization
  - From: Mateusz Guzik

Prev by Date: Re: [PATCH RFC v2 00/19] fuse: fuse-over-io-uring
Next by Date: Re: [PATCH v2 2/4] fs: add FS_IOC_FSSETXATTRAT and FS_IOC_FSGETXATTRAT
Previous by thread: [PATCH v2 4/4] bcachefs: remove now spurious i_state initialization
Next by thread: Re: [PATCH v2 0/4] inode_init_always zeroing i_state
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux