On Mon 07-01-19 22:07:43, Tetsuo Handa wrote: > On 2019/01/07 20:41, Michal Hocko wrote: > > On Sun 06-01-19 15:02:24, Tetsuo Handa wrote: > >> Michal and Johannes, can we please stop this stupid behavior now? > > > > I have proposed a patch with a much more limited scope which is still > > waiting for feedback. I haven't heard it wouldn't be working so far. > > > > You mean > > mutex_lock_killable would take care of exiting task already. I would > then still prefer to check for mark_oom_victim because that is not racy > with the exit path clearing signals. I can update my patch to use > _killable lock variant if we are really going with the memcg specific > fix. > > ? No response for two months. I mean http://lkml.kernel.org/r/20181022071323.9550-1-mhocko@xxxxxxxxxx which has died in nit picking. I am not very interested to go back there and spend a lot of time with it again. If you do not respect my opinion as the maintainer of this code then find somebody else to push it through. -- Michal Hocko SUSE Labs
