From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Security Officers <security@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
stable <stable@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix: compat_rw_copy_check_uvector() misuse in aio, readv, writev, and security keys
Date: Wed, 13 Mar 2013 09:53:04 -0400 [thread overview]
Message-ID: <20130313135304.GC15843@Krystal> (raw)
In-Reply-To: <CA+55aFy3gTpxzghYL6-Z4wYpubokFdQCYYZQ5tsJAr042uwgHw@mail.gmail.com>
* Linus Torvalds (torvalds@linux-foundation.org) wrote:
> On Tue, Mar 12, 2013 at 11:04 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > That said, the patch definitely looks like the right thing to do. I'll apply it.
>
> Hmm. I applied it, and then pretty much immediately realized what was
> problematic about it. What about the fs/bio.c one? This all felt like
> it was still a work-in-progress, and I'm not sure if you had more
> comments or patches coming along?
>
> Anyway, this particular patch got applied. Does that obviate the need
> for the fs/bio.c one? I didn't follow all the call-chains...
The fs/bio.c issue is unrelated to this patch, so that separate issue
still stands. I did not get any feedback on that private RFC though.
Should I repost it CCing lkml ?
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2013-03-13 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 15:20 [PATCH] Fix: compat_rw_copy_check_uvector() misuse in aio, readv, writev, and security keys Mathieu Desnoyers
2013-03-11 20:46 ` Greg Kroah-Hartman
2013-03-11 20:53 ` Mathieu Desnoyers
2013-03-12 18:04 ` Linus Torvalds
2013-03-12 18:23 ` Linus Torvalds
2013-03-13 13:53 ` Mathieu Desnoyers [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=20130313135304.GC15843@Krystal \
--to=mathieu.desnoyers@efficios.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=security@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).