[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMGZ=E7rUQ2iiBW+EJaj8ehWohKM5bN2V3t6Uk=kxWSD00OSg@mail.gmail.com>
Date: Sat, 15 Apr 2017 08:41:04 +0200
From: Vegard Nossum <vegard.nossum@...il.com>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [git pull] vfs fixes
On 9 April 2017 at 07:40, Al Viro <viro@...iv.linux.org.uk> wrote:
>
> The following changes since commit a71c9a1c779f2499fb2afc0553e543f18aff6edf:
>
> Linux 4.11-rc5 (2017-04-02 17:23:54 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus
>
> for you to fetch changes up to a8e28440016bfb23bec266c4c66eacca6ea2d48b:
>
> Merge branch 'work.statx' into for-next (2017-04-03 01:06:59 -0400)
>
> ----------------------------------------------------------------
> Al Viro (2):
> alpha: fix stack smashing in old_adjtimex(2)
> Merge branch 'work.statx' into for-next
I'm seeing the same memfd_create/name_to_handle_at/path_lookupat
use-after-free that Dmitry was seeing here:
https://lkml.org/lkml/2017/3/4/118
I haven't tried the patch from that thread yet, but was there any
reason for it not to get merged so far?
Vegard
Powered by blists - more mailing lists