On Wed 10-10-18 09:12:45, Tetsuo Handa wrote: > syzbot is hitting RCU stall due to memcg-OOM event. > https://syzkaller.appspot.com/bug?id=4ae3fff7fcf4c33a47c1192d2d62d2e03efffa64 This is really interesting. If we do not have any eligible oom victim we simply force the charge (allow to proceed and go over the hard limit) and break the isolation. That means that the caller gets back to running and realease all locks take on the way. I am wondering how come we are seeing the RCU stall. Whole is holding the rcu lock? Certainly not the charge patch and neither should the caller because you have to be in a sleepable context to trigger the OOM killer. So there must be something more going on. > What should we do if memcg-OOM found no killable task because the allocating task > was oom_score_adj == -1000 ? Flooding printk() until RCU stall watchdog fires > (which seems to be caused by commit 3100dab2aa09dc6e ("mm: memcontrol: print proper > OOM header when no eligible victim left") because syzbot was terminating the test > upon WARN(1) removed by that commit) is not a good behavior. We definitely want to inform about ineligible oom victim. We might consider some rate limiting for the memcg state but that is a valuable information to see under normal situation (when you do not have floods of these situations). -- Michal Hocko SUSE Labs
