[lkml]   [2010]   [Sep]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
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.

 \ /
  Last update: 2010-09-09 07:05    [W:0.126 / U:2.808 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site