From: Joe Perches <joe@perches.com>
To: Fabian Frederick <fabf@skynet.be>, Tejun Heo <tj@kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/1] kernel/workqueue.c: pr_warning/pr_warn & printk/pr_info
Date: Mon, 12 May 2014 11:21:28 -0700 [thread overview]
Message-ID: <1399918888.9240.28.camel@joe-AO725> (raw)
In-Reply-To: <20140512195623.bedc6e41683596d8d3b486c7@skynet.be>
On Mon, 2014-05-12 at 19:56 +0200, Fabian Frederick wrote:
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Fabian Frederick <fabf@skynet.be>
> ---
> kernel/workqueue.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> index 0ee63af..6824afc 100644
> --- a/kernel/workqueue.c
> +++ b/kernel/workqueue.c
> @@ -4098,8 +4098,8 @@ static void wq_update_unbound_numa(struct workqueue_struct *wq, int cpu,
> /* create a new pwq */
> pwq = alloc_unbound_pwq(wq, target_attrs);
> if (!pwq) {
> - pr_warning("workqueue: allocation failed while updating NUMA affinity of \"%s\"\n",
> - wq->name);
> + pr_warn("workqueue: allocation failed while updating NUMA affinity of \"%s\"\n",
> + wq->name);
> goto out_unlock;
> }
>
> @@ -4548,7 +4548,7 @@ void print_worker_info(const char *log_lvl, struct task_struct *task)
> probe_kernel_read(desc, worker->desc, sizeof(desc) - 1);
>
> if (fn || name[0] || desc[0]) {
> - printk("%sWorkqueue: %s %pf", log_lvl, name, fn);
> + pr_info("%sWorkqueue: %s %pf", log_lvl, name, fn);
Not correct.
log_lvl already emits the appropriate level
and this overrides it with KERN_INFO.
The output will now be incorrect emitting
at KERN_INFO followed by an SOH and the
desired log level.
> if (desc[0])
> pr_cont(" (%s)", desc);
> pr_cont("\n");
Trivially, it likely would be a bit better to avoid
any possible output message interleaving by using:
if (fn || name[0] || desc[0]) {
if (desc[0])
printk("%sWorkqueue: %s %pf (%s)\n",
log_lvl, name, fn, desc);
else
printk("%sWorkqueue: %s %pf\n",
log_lvl, name, fn);
}
next prev parent reply other threads:[~2014-05-12 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 17:56 Fabian Frederick
2014-05-12 18:01 ` Tejun Heo
2014-05-12 18:21 ` Joe Perches [this message]
2014-05-12 18:26 ` Fabian Frederick
2014-05-12 18:29 ` 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=1399918888.9240.28.camel@joe-AO725 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=fabf@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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
all inboxes | Powered by JetHome®