Messages in this thread | | | Date | Wed, 22 Jun 2016 14:15:51 +0200 | From | Michal Hocko <> | Subject | Re: mm, oom_reaper: How to handle race with oom_killer_disable() ? |
| |
On Wed 22-06-16 14:08:43, Michal Hocko wrote: > On Wed 22-06-16 19:57:17, Tetsuo Handa wrote: > > Michal Hocko wrote: > [...] > > > That being said I guess the patch to try_to_freeze_tasks after > > > oom_killer_disable should be simple enough to go for now and stable > > > trees and we can come up with something less hackish later. I do not > > > like the fact that oom_killer_disable doesn't act as a full "barrier" > > > anymore. > > > > > > What do you think? > > > > I'm OK with calling try_to_freeze_tasks(true) again for Linux 4.6 and 4.7 kernels. > > OK, I will resend the patch CC Rafael and stable.
Ohh, I've just realized that 449d777d7ad6 ("mm, oom_reaper: clear TIF_MEMDIE for all tasks queued for oom_reaper") went in in this merge window. So I've asked to push it to the next 4.7 rc. -- Michal Hocko SUSE Labs
| |