From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752669AbdGHHfL (ORCPT <rfc822;w@1wt.eu>);
        Sat, 8 Jul 2017 03:35:11 -0400
Received: from zeniv.linux.org.uk ([195.92.253.2]:45628 "EHLO
        ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751078AbdGHHfJ (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 8 Jul 2017 03:35:09 -0400
Date: Sat, 8 Jul 2017 08:35:06 +0100
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [git pull] vfs.git pile 13 - killing __copy_in_user()
Message-ID: <20170708073506.GO10672@ZenIV.linux.org.uk>
References: <20170708002954.GL10672@ZenIV.linux.org.uk>
 <CA+55aFw-LV1UKLUs=LFTVGa1yRcTd5554AcJVyLDrTmqf=+FJw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+55aFw-LV1UKLUs=LFTVGa1yRcTd5554AcJVyLDrTmqf=+FJw@mail.gmail.com>
User-Agent: Mutt/1.8.0 (2017-02-23)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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@zeniv.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...