Re: [PATCH -mm 1/3] mm/oom_kill: remove the wrongfatal_signal_pending()

From: Tetsuo Handa
Date: Wed Sep 30 2015 - 11:21:29 EST

Oleg Nesterov wrote:
> > This fatal_signal_pending() check is about to be added by me because the OOM
> > killer spams the kernel log when the mm struct which the OOM victim is using
> > is shared by many threads. ( )
> OK, I see, but it is wrong.
> But I don't really understand "shared by many threads", I mean "threads" is
> confusing word. I guess you mean CLONE_VM processes, otherwise we shouldn't
> see the additional spam.


> And 1000 CLONE_VM processes + "and the lock dependency prevents all threads
> except the OOM victim thread from terminating until they get TIF_MEMDIE flag"
> look like a really pathological case...

Right. But I saw that
took 3 minites to kill one mm struct because dump_header() was called for many

> > I was waiting for your comment about whether you depend on
> > the "sharing same memory" message with KERN_ERR level.
> > ( )
> >
> > If nobody else objects, I think we can remove the "sharing same memory"
> > message. ( )
> OK, will you agree with v2 which also removes pr_warn?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at