linux-kernel - Re: [git pull] vfs.git

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CA+55aFyO_HXDqo7Lh_OSUJJXWdQc4ccOFeky31r+QwUsyN1bDg@mail.gmail.com>
Date:	Sat, 19 Mar 2016 18:55:21 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Al Viro <viro@...iv.linux.org.uk>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [git pull] vfs.git

On Sat, Mar 19, 2016 at 6:44 PM, Al Viro <viro@...iv.linux.org.uk> wrote:
>         Preparations of parallel lookups (the remaining main obstacle is the
> need to move security_d_instantiate(); once that becomes safe, the rest will
> be a matter of rather short series local to fs/*.c) + preadv2/pwritev2 series
> from Christoph + assorted fixes.

So this:

> Al Viro:
>       replace d_add_unique() with saner primitive

ends up conflicting with commit d9dfd8d74168 ("NFSv4: Fix a dentry
leak on alias use").

>From what I can tell, your version doesn't have the leak issue, so my
merge resolution is to just take your new code as-is, but I'd ask you
to double-check my logic.

(I haven't pushed out the merge yet, it's still going through my build
test. Soon, but I guess you can just take a look at that dentry leak
commit regardless).

                  Linus