From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965438AbbI2OVd (ORCPT ); Tue, 29 Sep 2015 10:21:33 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52425 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965059AbbI2OVY (ORCPT ); Tue, 29 Sep 2015 10:21:24 -0400 Date: Tue, 29 Sep 2015 16:18:15 +0200 From: Oleg Nesterov To: Andrew Morton Cc: David Rientjes , Kyle Walker , Michal Hocko , Stanislav Kozina , Tetsuo Handa , linux-kernel@vger.kernel.org Subject: [PATCH -mm 1/3] mm/oom_kill: remove the wrong fatal_signal_pending() Message-ID: <20150929141815.GA10952@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150929141758.GA10934@redhat.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The fatal_signal_pending() was added to suppress unnecessary "sharing same memory" message, but it can't 100% help anyway because it can be false-negative; SIGKILL can be already dequeued. And worse, it can be false-positive due to exec or coredump. exec is mostly fine, but coredump is not. It is possible that the group leader has the pending SIGKILL because its sub-thread originated the coredump, in this case we must not skip this process. We could probably add the additional ->group_exit_task check but this pach just removes fatal_signal_pending(), the extra "Kill process" is unlikely and doesn't really hurt. Signed-off-by: Oleg Nesterov --- mm/oom_kill.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/mm/oom_kill.c b/mm/oom_kill.c index 4766e25..0d581c6 100644 --- a/mm/oom_kill.c +++ b/mm/oom_kill.c @@ -588,8 +588,6 @@ void oom_kill_process(struct oom_control *oc, struct task_struct *p, !(p->flags & PF_KTHREAD)) { if (p->signal->oom_score_adj == OOM_SCORE_ADJ_MIN) continue; - if (fatal_signal_pending(p)) - continue; pr_info("Kill process %d (%s) sharing same memory\n", task_pid_nr(p), p->comm); -- 2.4.3