Re: [PATCH] oom: always panic on OOM when panic_on_oom is configured

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Newsgroups	linux.kernel
Subject	Re: [PATCH] oom: always panic on OOM when panic_on_oom is configured
Date	Mon, 08 Jun 2015 14:00:03 +0200
Message-ID	<pz3SH-64a-7@gated-at.bofh.it> (permalink)
References	<pwwxS-zk-57@gated-at.bofh.it> <pxMAy-7hJ-11@gated-at.bofh.it> <pxXPj-6Ru-5@gated-at.bofh.it> <pygff-FK-15@gated-at.bofh.it> <pz0Br-1lC-11@gated-at.bofh.it>
X-Original-To	mhocko@suse.cz
X-Virus-Status	clean(F-Secure/virusgw_smtp/412/fsav303.sakura.ne.jp)
X-Mailer	Winbiff [Version 2.51 PL2]
X-Accept-Language	ja,en,zh
MIME-Version	1.0
Content-Type	text/plain; charset=us-ascii
Sender	robomod@news.nic.it
List-ID	<linux-kernel.vger.kernel.org>
X-Mailing-List	linux-kernel@vger.kernel.org
Approved	robomod@news.nic.it
Lines	25
Organization	linux.* mail to news gateway
X-Original-Cc	rientjes@google.com, akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org
X-Original-Date	Mon, 8 Jun 2015 20:53:18 +0900
X-Original-Message-ID	<201506082053.IIF18706.JFFFHOQtMLOSVO@I-love.SAKURA.ne.jp>
X-Original-References	<1433159948-9912-1-git-send-email-mhocko@suse.cz> <alpine.DEB.2.10.1506041607020.16555@chino.kir.corp.google.com> <20150605111302.GB26113@dhcp22.suse.cz> <201506061551.BHH48489.QHFOMtFLSOFOJV@I-love.SAKURA.ne.jp> <20150608082137.GD1380@dhcp22.suse.cz>
X-Original-Sender	linux-kernel-owner@vger.kernel.org
Xref	aioe.org linux.kernel:1160422

Show key headers only | View raw

Michal Hocko wrote:
> On Sat 06-06-15 15:51:35, Tetsuo Handa wrote:
> > For me, !__GFP_FS allocations not calling out_of_memory() _forever_ is a
> > violation of the user policy.
> 
> Yes, the current behavior of GFP_NOFS is highly suboptimal, but this has
> _nothing_ what so ever to do with this patch and panic_on_oom handling.
> The former one is the page allocator proper while we are in the OOM
> killer layer here.
> 
> This is not the first time you have done that. Please stop it. It makes
> a complete mess of the original discussions.

My specific area of expertise in Linux kernel is security/tomoyo/ directory.
What I could contribute with other areas is to pay attention to potential
possibilities. But I'm such outsider about other areas that I can't
differentiate the page allocator proper from the OOM killer layer.

Excuse me for focusing on the wrong issue, but I will likely unconsciously
make the same mistake again. Please ignore or point out when I made mistakes.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Thread

Re: [PATCH] oom: always panic on OOM when panic_on_oom is  configured David Rientjes <rientjes@google.com> - 2015-06-05 01:20 +0200
  Re: [PATCH] oom: always panic on OOM when panic_on_oom is configured Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> - 2015-06-08 14:00 +0200
  Re: [PATCH] oom: always panic on OOM when panic_on_oom is  configured David Rientjes <rientjes@google.com> - 2015-06-08 22:00 +0200
    Re: [PATCH] oom: always panic on OOM when panic_on_oom is  configured David Rientjes <rientjes@google.com> - 2015-06-11 02:40 +0200
  Re: [PATCH] oom: always panic on OOM when panic_on_oom is  configured David Rientjes <rientjes@google.com> - 2015-06-08 22:00 +0200

csiph-web