linux-kernel - Re: [PATCH] Fix: compat_rw_copy_check_uvector() misuse in aio, readv, writev, and security keys

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

Date:	Tue, 12 Mar 2013 11:23:41 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
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

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

                   Linus
--
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/