linux-kernel - Re: Commit "new primitive: discard_new

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: <20180801161151.GO30522@ZenIV.linux.org.uk>
Date:   Wed, 1 Aug 2018 17:11:51 +0100
From:   Al Viro <viro@...IV.linux.org.uk>
To:     Kirill Tkhai <ktkhai@...tuozzo.com>
Cc:     "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: Commit "new primitive: discard_new_inode()" introduces a problem

On Wed, Aug 01, 2018 at 06:43:56PM +0300, Kirill Tkhai wrote:
> #git status
> HEAD detached at 22dc9a168272

Wait a sec - just that commit?  With discard_new_inode() not even
used anywhere?  Then any of those -ENOMEM is disguised ERR_PTR(-ESTALE)
from find_inode()/find_inode_fast(), i.e. an inode found by
iget5_locked() (your /etc is on ext4) with I_CREATING still set.
And that is set only by insert_inode_locked()/insert_inode_locked4(),
and only until unlock_new_inode().

Could you slap WARN_ON(1) before these return ERR_PTR(-ESTALE) in
find_inode{,_fast}() and see if that's what's getting triggered?