Messages in this thread | | | Date | Sun, 20 Sep 2015 11:05:04 -0700 | Subject | Re: can't oom-kill zap the victim's memory? | From | Linus Torvalds <> |
| |
On Sun, Sep 20, 2015 at 5:56 AM, Oleg Nesterov <oleg@redhat.com> wrote: > > In this case the workqueue thread will block.
What workqueue thread?
pagefault_out_of_memory -> out_of_memory -> oom_kill_process
as far as I can tell, this can be called by any task. Now, that pagefault case should only happen when the page fault comes from user space, but we also have
__alloc_pages_slowpath -> __alloc_pages_may_oom -> out_of_memory -> oom_kill_process
which can be called from just about any context (but atomic allocations will never get here, so it can schedule etc).
So what's your point? Explain again just how do you guarantee that you can take the mmap_sem.
Linus
| |