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()
Date: Sat, 8 Jul 2017 08:35:06 +0100 [thread overview]
Message-ID: <20170708073506.GO10672@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFw-LV1UKLUs=LFTVGa1yRcTd5554AcJVyLDrTmqf=+FJw@mail.gmail.com>
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...
prev parent reply other threads:[~2017-07-08 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 0:29 [git pull] vfs.git pile 13 - killing __copy_in_user() Al Viro
2017-07-08 5:27 ` Linus Torvalds
2017-07-08 7:35 ` Al Viro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170708073506.GO10672@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.