linux-kernel - Re: [PATCH] oom: add uid to "Killed process" message

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 20 Jun 2011 14:09:19 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Frantisek Hrbata <fhrbata@...hat.com>
cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Minchan Kim <minchan.kim@...il.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	CAI Qian <caiqian@...hat.com>, lwoodman@...hat.com
Subject: Re: [PATCH] oom: add uid to "Killed process" message

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.

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?
--
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/