From: Joe Perches <joe@perches.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm/page_alloc: Avoid KERN_CONT uses in warn_alloc
Date: Thu, 09 Nov 2017 08:27:33 -0800 [thread overview]
Message-ID: <1510244853.15768.64.camel@perches.com> (raw)
In-Reply-To: <20171109100531.3cn2hcqnuj7mjaju@dhcp22.suse.cz>
On Thu, 2017-11-09 at 11:05 +0100, Michal Hocko wrote:
[]
> Subject: [PATCH] mm: simplify nodemask printing
>
> alloc_warn and dump_header have to explicitly handle NULL nodemask which
> forces both paths to use pr_cont. We can do better. printk already
> handles NULL pointers properly so all what we need is to teach
> nodemask_pr_args to handle NULL nodemask carefully. This allows
> simplification of both alloc_warn and dump_header and get rid of pr_cont
> altogether.
[]
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
[]
> @@ -426,14 +426,10 @@ static void dump_tasks(struct mem_cgroup *memcg, const nodemask_t *nodemask)
>
> static void dump_header(struct oom_control *oc, struct task_struct *p)
> {
> - pr_warn("%s invoked oom-killer: gfp_mask=%#x(%pGg), nodemask=",
> - current->comm, oc->gfp_mask, &oc->gfp_mask);
> - if (oc->nodemask)
> - pr_cont("%*pbl", nodemask_pr_args(oc->nodemask));
> - else
> - pr_cont("(null)");
> - pr_cont(", order=%d, oom_score_adj=%hd\n",
> - oc->order, current->signal->oom_score_adj);
> + pr_warn("%s invoked oom-killer: gfp_mask=%#x(%pGg), nodemask=%*pbl, order=%d, oom_score_adj=%hd\n",
> + current->comm, oc->gfp_mask, &oc->gfp_mask,
> + nodemask_pr_args(oc->nodemask), oc->order,
> + current->signal->oom_score_adj);
trivia:
You could align the arguments to the open parenthesis here
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
[]
> @@ -3281,20 +3281,14 @@ void warn_alloc(gfp_t gfp_mask, nodemask_t *nodemask, const char *fmt, ...)
> if ((gfp_mask & __GFP_NOWARN) || !__ratelimit(&nopage_rs))
> return;
>
> - pr_warn("%s: ", current->comm);
> -
> va_start(args, fmt);
> vaf.fmt = fmt;
> vaf.va = &args;
> - pr_cont("%pV", &vaf);
> + pr_warn("%s: %pV, mode:%#x(%pGg), nodemask=%*pbl\n",
> + current->comm, &vaf, gfp_mask, &gfp_mask,
> + nodemask_pr_args(nodemask));
and here
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm/page_alloc: Avoid KERN_CONT uses in warn_alloc
Date: Thu, 09 Nov 2017 08:27:33 -0800 [thread overview]
Message-ID: <1510244853.15768.64.camel@perches.com> (raw)
In-Reply-To: <20171109100531.3cn2hcqnuj7mjaju@dhcp22.suse.cz>
On Thu, 2017-11-09 at 11:05 +0100, Michal Hocko wrote:
[]
> Subject: [PATCH] mm: simplify nodemask printing
>
> alloc_warn and dump_header have to explicitly handle NULL nodemask which
> forces both paths to use pr_cont. We can do better. printk already
> handles NULL pointers properly so all what we need is to teach
> nodemask_pr_args to handle NULL nodemask carefully. This allows
> simplification of both alloc_warn and dump_header and get rid of pr_cont
> altogether.
[]
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
[]
> @@ -426,14 +426,10 @@ static void dump_tasks(struct mem_cgroup *memcg, const nodemask_t *nodemask)
>
> static void dump_header(struct oom_control *oc, struct task_struct *p)
> {
> - pr_warn("%s invoked oom-killer: gfp_mask=%#x(%pGg), nodemask=",
> - current->comm, oc->gfp_mask, &oc->gfp_mask);
> - if (oc->nodemask)
> - pr_cont("%*pbl", nodemask_pr_args(oc->nodemask));
> - else
> - pr_cont("(null)");
> - pr_cont(", order=%d, oom_score_adj=%hd\n",
> - oc->order, current->signal->oom_score_adj);
> + pr_warn("%s invoked oom-killer: gfp_mask=%#x(%pGg), nodemask=%*pbl, order=%d, oom_score_adj=%hd\n",
> + current->comm, oc->gfp_mask, &oc->gfp_mask,
> + nodemask_pr_args(oc->nodemask), oc->order,
> + current->signal->oom_score_adj);
trivia:
You could align the arguments to the open parenthesis here
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
[]
> @@ -3281,20 +3281,14 @@ void warn_alloc(gfp_t gfp_mask, nodemask_t *nodemask, const char *fmt, ...)
> if ((gfp_mask & __GFP_NOWARN) || !__ratelimit(&nopage_rs))
> return;
>
> - pr_warn("%s: ", current->comm);
> -
> va_start(args, fmt);
> vaf.fmt = fmt;
> vaf.va = &args;
> - pr_cont("%pV", &vaf);
> + pr_warn("%s: %pV, mode:%#x(%pGg), nodemask=%*pbl\n",
> + current->comm, &vaf, gfp_mask, &gfp_mask,
> + nodemask_pr_args(nodemask));
and here
next prev parent reply other threads:[~2017-11-09 16:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 18:02 [PATCH] mm/page_alloc: Avoid KERN_CONT uses in warn_alloc Joe Perches
2017-11-06 18:02 ` Joe Perches
2017-11-07 12:50 ` Michal Hocko
2017-11-07 12:50 ` Michal Hocko
2017-11-07 15:34 ` Joe Perches
2017-11-07 15:34 ` Joe Perches
2017-11-07 15:43 ` Michal Hocko
2017-11-07 15:43 ` Michal Hocko
2017-11-07 16:03 ` Joe Perches
2017-11-07 16:03 ` Joe Perches
2017-11-09 10:05 ` Michal Hocko
2017-11-09 10:05 ` Michal Hocko
2017-11-09 15:49 ` Joe Perches
2017-11-09 15:49 ` Joe Perches
2017-11-09 16:03 ` Michal Hocko
2017-11-09 16:03 ` Michal Hocko
2017-11-09 16:27 ` Joe Perches [this message]
2017-11-09 16:27 ` Joe Perches
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=1510244853.15768.64.camel@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.