[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130313135304.GC15843@Krystal>
Date: Wed, 13 Mar 2013 09:53:04 -0400
From: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Security Officers <security@...nel.org>,
Al Viro <viro@...iv.linux.org.uk>,
stable <stable@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Fix: compat_rw_copy_check_uvector() misuse in aio,
readv, writev, and security keys
* Linus Torvalds (torvalds@...ux-foundation.org) wrote:
> On Tue, Mar 12, 2013 at 11:04 AM, Linus Torvalds
> <torvalds@...ux-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
--
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/
Powered by blists - more mailing lists