Date: Wed, 8 Sep 2010 12:00:42 +0900 (JST) From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> To: Roland McGrath <roland@...hat.com> Cc: kosaki.motohiro@...fujitsu.com, Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, oss-security@...ts.openwall.com, Solar Designer <solar@...nwall.com>, Kees Cook <kees.cook@...onical.com>, Al Viro <viro@...iv.linux.org.uk>, Oleg Nesterov <oleg@...hat.com>, Neil Horman <nhorman@...driver.com>, linux-fsdevel@...r.kernel.org, pageexec@...email.hu, "Brad Spengler <spender@...ecurity.net> Eugene Teo" <eugene@...hat.com> Subject: Re: [PATCH 0/3] execve argument-copying fixes > This is my take on parts of the execve large arguments copying issues > that Kees posted about, and Brad and others have been discussing. > I've only looked at the narrow area of the argument copying code > itself. I think these are good and necessary fixes. But I'm not > addressing the whole OOM killer/mm accounting issue, which also needs > to be fixed (and I have the impression others are already looking into that). > > The following changes since commit d56557af19867edb8c0e96f8e26399698a08857f: > > Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6 (2010-09-07 16:00:17 -0700) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/frob/linux-2.6-roland.git topic/exec-fixes > > Roland McGrath (3): > setup_arg_pages: diagnose excessive argument size > execve: improve interactivity with large arguments > execve: make responsive to SIGKILL with large arguments > > fs/exec.c | 14 ++++++++++++++ > 1 files changed, 14 insertions(+), 0 deletions(-) All of changes looks nice to me :) Thanks. Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Powered by blists - more mailing lists
Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.