linux-kernel - Re: [git pull] more vfs bits

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: <CA+55aFw4JNWxvDf9Ojk64+YhyqnubwAF-mUoH2hBQxL+5mGUig@mail.gmail.com>
Date:	Sat, 21 Feb 2015 19:16:16 -0800
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] more vfs bits

On Sat, Feb 21, 2015 at 6:51 PM, Al Viro <viro@...iv.linux.org.uk> wrote:
>
> Umm...  Works for me.  Let's do it this way, then:
>         * rename those guys through the whole series
>         * leave the "annotate the filesystems" bits to sit in a vfs.git
> branch
>         * slap trylock_super() + bugfixes I'd been doing today
> (procfs and debugfs symlink removals racing with follow_link, oopsable;
> double-copy in autofs dev_ioctl.c, with length not rechecked after
> copying, theoretically oopsable + reasonably likely data leak) on top of queue
>         * feed it through local tests and send an updated pull request later
> tonight.

Ok, I guess I can live with that.

                       Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/