On Wed 27-02-19 12:43:51, Tetsuo Handa wrote: > I noticed that when a kdump kernel triggers the OOM killer because a too > small value was given to crashkernel= parameter, the OOM reaper tends to > fail to reclaim memory from OOM victims because they are in dup_mm() from > copy_mm() from copy_process() with mmap_sem held for write. I would presume that a page table allocation would fail for the oom victim as soon as the oom memory reserves get depleted and then copy_page_range would bail out and release the lock. That being said, the oom_reaper might bail out before then but does sprinkling fatal_signal_pending checks into copy_*_range really help reliably? -- Michal Hocko SUSE Labs
