linux-kernel - Re: [PATCH v2 2/4] vfs: partially sanitize i

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20240613-frieden-datteln-afe55df1359b@brauner>
Date: Thu, 13 Jun 2024 13:41:20 +0200
From: Christian Brauner <brauner@...nel.org>
To: Jan Kara <jack@...e.cz>
Cc: Mateusz Guzik <mjguzik@...il.com>, viro@...iv.linux.org.uk, 
	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
Subject: Re: [PATCH v2 2/4] vfs: partially sanitize i_state zeroing on inode
 creation

> This would be more logical above where inode content is initialized (and
> less errorprone just in case security_inode_alloc() grows dependency on
> i_state value) - like just after:
> 
> 	inode->i_flags = 0;

Fixed that in-tree. Thanks!