From: Frantisek Hrbata <fhrbata@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
CAI Qian <caiqian@redhat.com>,
lwoodman@redhat.com
Subject: Re: [PATCH] oom: add uid to "Killed process" message
Date: Tue, 21 Jun 2011 13:36:29 +0200 [thread overview]
Message-ID: <20110621113629.GA2758@dhcp-26-164.brq.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1106201409090.2639@chino.kir.corp.google.com>
On Mon, Jun 20, 2011 at 02:09:19PM -0700, David Rientjes wrote:
> On Mon, 20 Jun 2011, Frantisek Hrbata wrote:
>
> > Add user id to the oom killer's "Killed process" message, so the user of the
> > killed process can be identified.
> >
>
> Notified in what way? Unless you are using the memory controller, there's
> no userspace notification that an oom event has happened so nothing would
> know to scrape the kernel log for this information.
Agreed, but this is not primary about notification, but about the availability of
the information at all, even if it's just in the kernel log and there is no
realtime notification about it. If I'm not missing anything, now you are not
notified if some process is killed neither(unless as you mentioned, you use
eventfd for memory.oom_control). But you can always inspect the kernel log
afterwards when you find out that some process is not running and you want to
know what happened. And here you have the information that the process was
killed by the oom killer.
I guess the uid of the killed process can be identified from the dump_tasks
output, where it is presented along with other info. I think it is handy
to have the uid info directly in the "Killed process" message.
This is used/requested by one of our customers and since I think it's a good
idea to have the uid info presented, I posted the patch here to see what do you
think about it.
Many thanks
>
> We've had a long-time desire for an oom notifier, not only at the time of
> oom but when approaching it with configurable thresholds, that would
> wakeup a userspace daemon that might be polling on notifier. That seems
> more useful for realtime notification of an oom event rather than relying
> on the kernel log?
--
Frantisek Hrbata
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-06-21 11:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 11:04 [PATCH] oom: add uid to "Killed process" message Frantisek Hrbata
2011-06-20 21:09 ` David Rientjes
2011-06-21 11:36 ` Frantisek Hrbata [this message]
2011-06-21 19:07 ` David Rientjes
-- strict thread matches above, loose matches on Subject: below --
2011-06-20 10:16 Frantisek Hrbata
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=20110621113629.GA2758@dhcp-26-164.brq.redhat.com \
--to=fhrbata@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=caiqian@redhat.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lwoodman@redhat.com \
--cc=minchan.kim@gmail.com \
--cc=rientjes@google.com \
/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;
as well as URLs for NNTP newsgroup(s).