From: David Rientjes <rientjes@google.com>
To: Sha Zhengju <handai.szj@gmail.com>
Cc: linux-mm@kvack.org, cgroups@vger.kernel.org,
Sha Zhengju <handai.szj@taobao.com>,
kamezawa.hiroyu@jp.fujitsu.com, akpm@linux-foundation.org,
mhocko@suse.cz, gthelen@google.com, hannes@cmpxchg.org
Subject: Re: [PATCH 2/2] memcg, oom: Clarify some oom dump messages
Date: Tue, 31 Jul 2012 20:55:01 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1207312052070.20073@chino.kir.corp.google.com> (raw)
In-Reply-To: <1343146334-15161-1-git-send-email-handai.szj@taobao.com>
On Wed, 25 Jul 2012, Sha Zhengju wrote:
> From: Sha Zhengju <handai.szj@taobao.com>
>
> Revise some oom dump messages to avoid misleading admin.
>
The only place the oom killer emits information on what it does via the
kernel log so changing this has the potential for messing up a number of
scripts that people are using for parsing it (this would break some of our
log scraping code, for instance).
This adds nothing except a bogus message that is emitted when
select_bad_process() races with oom_kill_process() and no kill occurs
because all threads of the selected process have detached their mm.
Nack.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-08-01 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 16:09 [PATCH 1/2] memcg, oom: Provide more info while memcg oom happening Sha Zhengju
2012-07-24 16:12 ` [PATCH 2/2] memcg, oom: Clarify some oom dump messages Sha Zhengju
2012-08-01 3:55 ` David Rientjes [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1207312052070.20073@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=gthelen@google.com \
--cc=handai.szj@gmail.com \
--cc=handai.szj@taobao.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox