Date: Thu, 9 Sep 2010 14:01:33 +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>, KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> Subject: [PATCH 0/2] execve memory exhaust of 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). Now, we have two OOM-Killer/mm acounting problem. 1) OOM-killer doesn't track nascent mm and It may kill innocent task 2) When execve argument-copying, our __vm_enough_memory() doesn't protect any wrong plenty argument. then, execve() invoke OOM instead return failure value when larger argument than system memory. The patch series addressed this two issue.
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.