From: Michal Hocko <mhocko@kernel.org>
To: Joel Savitz <jsavitz@redhat.com>
Cc: linux-kernel@vger.kernel.org, Rafael Aquini <aquini@redhat.com>
Subject: Re: [PATCH] mm/oom_killer: Add task UID to info message on an oom kill
Date: Mon, 29 Apr 2019 00:49:07 +0200 [thread overview]
Message-ID: <20190428224907.GC956@dhcp22.suse.cz> (raw)
In-Reply-To: <1556130013-19021-1-git-send-email-jsavitz@redhat.com>
On Wed 24-04-19 14:20:13, Joel Savitz wrote:
> In the event of an oom kill, useful information about the killed
> process is printed to dmesg. Users, especially system administrators,
> will find it useful to immediately see the UID of the process.
>
> In the following example, abuse_the_ram is the name of a program
> that attempts to iteratively allocate all available memory until it is
> stopped by force.
There was a more general rework of this message
http://lkml.kernel.org/r/1542799799-36184-1-git-send-email-ufo19890607@gmail.com
but I do not see it merged into Andrew's tree. Could you have a look and
pursue it, please?
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2019-04-28 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 18:20 [PATCH] mm/oom_killer: Add task UID to info message on an oom kill Joel Savitz
2019-04-25 20:59 ` Rafael Aquini
2019-04-25 22:45 ` David Rientjes
2019-04-28 22:49 ` Michal Hocko [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=20190428224907.GC956@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aquini@redhat.com \
--cc=jsavitz@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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