linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Stepan Bujnak <stepan@pex.com>
Cc: linux-mm@kvack.org, corbet@lwn.net, mcgrof@kernel.org,
	hannes@cmpxchg.org
Subject: Re: [PATCH] mm/oom: added option 'oom_dump_task_cmdline'
Date: Wed, 20 Feb 2019 07:49:39 +0100	[thread overview]
Message-ID: <20190220064939.GT4525@dhcp22.suse.cz> (raw)
In-Reply-To: <20190220032245.2413-1-stepan@pex.com>

On Wed 20-02-19 04:22:45, Stepan Bujnak wrote:
> When oom_dump_tasks is enabled, this option will try to display task
> cmdline instead of the command name in the system-wide task dump.
> 
> This is useful in some cases e.g. on postgres server. If OOM killer is
> invoked it will show a bunch of tasks called 'postgres'. With this
> option enabled it will show additional information like the database
> user, database name and what it is currently doing.
> 
> Other example is python. Instead of just 'python' it will also show the
> script name currently being executed.

The size of OOM report output is quite large already and this will just
add much more for some workloads and printing from this context is quite
a problem already.
 
> Signed-off-by: Stepan Bujnak <stepan@pex.com>
> ---
>  Documentation/sysctl/vm.txt | 10 ++++++++++
>  include/linux/oom.h         |  1 +
>  kernel/sysctl.c             |  7 +++++++
>  mm/oom_kill.c               | 20 ++++++++++++++++++--
>  4 files changed, 36 insertions(+), 2 deletions(-)
> 
[...]
> @@ -404,9 +406,18 @@ static void dump_tasks(struct mem_cgroup *memcg, const nodemask_t *nodemask)
>  	pr_info("[  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name\n");
>  	rcu_read_lock();
>  	for_each_process(p) {
> +		char *name, *cmd = NULL;
> +
>  		if (oom_unkillable_task(p, memcg, nodemask))
>  			continue;
>  
> +		/*
> +		 * This needs to be done before calling find_lock_task_mm()
> +		 * since both grab a task lock which would result in deadlock.
> +		 */
> +		if (sysctl_oom_dump_task_cmdline)
> +			cmd = kstrdup_quotable_cmdline(p, GFP_KERNEL);
> +
>  		task = find_lock_task_mm(p);
>  		if (!task) {
>  			/*
You are trying to allocate from the OOM context. That is a big no no.
Not to mention that this is deadlock prone because get_cmdline needs
mmap_sem and the allocating context migh hold the lock already. So the
patch is simply wrong.

-- 
Michal Hocko
SUSE Labs


  parent reply	other threads:[~2019-02-20  6:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20  3:22 Stepan Bujnak
2019-02-20  4:09 ` Randy Dunlap
2019-02-20  4:30   ` Bujnak, Stepan
2019-02-20  5:56     ` Randy Dunlap
2019-02-20  6:49 ` Michal Hocko [this message]
2019-02-20  8:37   ` Bujnak, Stepan
2019-02-20 10:00     ` Tetsuo Handa
2019-02-20 10:01     ` Michal Hocko

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=20190220064939.GT4525@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=corbet@lwn.net \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=mcgrof@kernel.org \
    --cc=stepan@pex.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