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

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

Message-ID: <20170708073506.GO10672@ZenIV.linux.org.uk>
Date:   Sat, 8 Jul 2017 08:35:06 +0100
From:   Al Viro <viro@...IV.linux.org.uk>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [git pull] vfs.git pile 13 - killing __copy_in_user()

On Fri, Jul 07, 2017 at 10:27:38PM -0700, Linus Torvalds wrote:
> On Fri, Jul 7, 2017 at 5:29 PM, Al Viro <viro@...iv.linux.org.uk> wrote:
> >         There used to be 6 places in the entire tree calling __copy_in_user(),
> > all of them bogus.  Four got killed off in work.drm branch, this takes care of
> > the remaining ones and kills the definition of that sucker.
> 
> This branch is garbage.
> 
> You seem to have merged in some *old* drm branch into it, so it has
> all those drm commits that I merged earlier, except they are not the
> *same* commits.

Huh?

<starts cursing>

42bf8be378270f85ca926452ec473e65ea26d94b is where vfs.git #work.__copy_in_user is
119d0312c766773ca3238b9d926077664eed22be is what mentioned in the pull request
and that's where the local branch is.

OK, force-pushed, should propagate in a few.  I wonder how I'd missed the warning
spewed by git request-pull - it did produce one...