Messages in this thread | | | Date | Thu, 16 Jan 2014 10:32:20 +0100 | From | Michal Hocko <> | Subject | Re: [patch 1/2] mm, memcg: avoid oom notification when current needs access to memory reserves |
| |
On Wed 15-01-14 13:23:10, David Rientjes wrote: > On Wed, 15 Jan 2014, Michal Hocko wrote: [...] > > Which depends on yours only to revert your part. I plan to repost it but > > that still doesn't mean it will get merged because Johannes still has > > some argumnets against. I would like to start the discussion again > > because now we are so deep in circles that it is hard to come up with a > > reasonable outcome. It is still hard to e.g. agree on an actual fix > > for a real problem https://lkml.org/lkml/2013/12/12/129. > > > > This is concerning because it's merged in -mm without being tested by Eric > and is marked for stable while violating the stable kernel rules criteria.
Are you questioning the patch fixes the described issue?
Please note that the exit_robust_list and PF_EXITING as a culprit has been identified by Eric. Of course I would prefer if it was tested by anybody who can reproduce it. -- Michal Hocko SUSE Labs
| |