fix premature OOM killer
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 20 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mm, oom: make sure that the oom victim uses memory reservesmm/ | +1 | 3 replies | |
| 2/2 | mm, oom: do not trigger out_of_memory from the #PFmm/ | +10 | 15 replies |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Michal Hocko | Roman Gushchin |
|---|---|---|
| 1/2 | A-b | T-b |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] fix premature OOM killer
Hi,
this is a follow up for [1]. The first patch is what Tetsuo suggested [2], I've just added a changelog for it. This one should be merged as soon as possible. The second patch is still an RFC. I _believe_ that it is the right thing to do but I haven't checked all the PF paths which return VM_FAULT_OOM to be sure that there is nobody who would return this error when not doing a real allocation.
[1] http://lkml.kernel.org/r/[email protected]
[2] http://lkml.kernel.org/r/[email protected]
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>