linux-kernel - Re: [RFC][PATCH] oom: Be less verbose if the oom

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.02.1406051358210.18119@chino.kir.corp.google.com>
Date:	Thu, 5 Jun 2014 14:01:02 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Michal Hocko <mhocko@...e.cz>
cc:	Richard Weinberger <richard@....at>, hannes@...xchg.org,
	bsingharora@...il.com, kamezawa.hiroyu@...fujitsu.com,
	akpm@...ux-foundation.org, vdavydov@...allels.com, tj@...nel.org,
	handai.szj@...bao.com, oleg@...hat.com, rusty@...tcorp.com.au,
	kirill.shutemov@...ux.intel.com, linux-kernel@...r.kernel.org,
	cgroups@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [RFC][PATCH] oom: Be less verbose if the oom_control event fd
 has listeners

On Thu, 5 Jun 2014, Michal Hocko wrote:

> If we are printing too much then OK, let's remove those parts which are
> not that useful but hiding information which tells us more about the oom
> decision doesn't sound right to me.
> 

Memcg oom killer printing is controlled mostly by 
mem_cgroup_print_oom_info(), I don't see anything in the generic oom 
killer that should be removed and that I have not used even for memcg ooms 
in the past.

Perhaps there could be a case made for suppressing some of the 
hierarchical stats from being printed for memcg ooms and controlled by 
another memcg knob, but it doesn't sound vital.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/