linux-kernel - Re: [PATCH v12 01/54] vfs: export new_inode

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <YkYF7XdrXoWrphGi@zeniv-ca.linux.org.uk>
Date:   Thu, 31 Mar 2022 19:50:05 +0000
From:   Al Viro <viro@...iv.linux.org.uk>
To:     Jeff Layton <jlayton@...nel.org>
Cc:     ceph-devel@...r.kernel.org, xiubli@...hat.com, idryomov@...il.com,
        lhenriques@...e.de, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v12 01/54] vfs: export new_inode_pseudo

On Thu, Mar 31, 2022 at 11:30:37AM -0400, Jeff Layton wrote:
> Ceph needs to be able to allocate inodes ahead of a create that might
> involve a fscrypt-encrypted inode. new_inode() almost fits the bill,
> but it puts the inode on the sb->s_inodes list and when we go to hash
> it, that might be done again.
> 
> We could work around that by setting I_CREATING on the new inode, but
> that causes ilookup5 to return -ESTALE if something tries to find it
> before I_NEW is cleared. This is desirable behavior for most
> filesystems, but doesn't work for ceph.
> 
> To work around all of this, just use new_inode_pseudo which doesn't add
> it to the sb->s_inodes list.

Umm...  I can live with that, but... why not just leave the hash insertion
until the thing is fully set up and you are ready to clear I_NEW?