LKML Archive on
help / color / mirror / Atom feed
From: Jan Engelhardt <>
To: Joe Perches <>
Cc: Pavel Emelyanov <>, Andrew Morton <>,
	Alexey Dobriyan <>,
	Linux Containers <>,,
	Linux Kernel Mailing List <>,
	Sukadev Bhattiprolu <>,
	Oleg Nesterov <>
Subject: Re: [PATCH] Use helpers to obtain task pid in printks (arch code)
Date: Thu, 30 Aug 2007 21:11:05 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0708302107510.24730@fbirervta.pbzchgretzou.qr> (raw)
In-Reply-To: <1188237708.18004.102.camel@localhost>

On Aug 27 2007 11:01, Joe Perches wrote:
>On Mon, 2007-08-27 at 11:30 +0400, Pavel Emelyanov wrote:
>> From: Alexey Dobriyan <>
>> One of the easiest things to isolate is the pid printed in kernel
>> log. There was a patch, that made this for arch-independent code,
>> this one makes so for arch/xxx files.
>Perhaps it would be worthwhile to standardize the printk
>task information content? Maybe a format knob?
>Maybe TASK_FMT/TASK_ARG(task)
>#define TASK_FMT "%s"
>#define TASK_ARG(tsk) ({char __buf[MAX_TASK_INFO]; print_task(tsk, buf, sizeof(__buf)); __buf})

Except that __buf goes out of scope before printk() is called...


      reply	other threads:[~2007-08-30 19:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-27  7:30 Pavel Emelyanov
2007-08-27 18:01 ` Joe Perches
2007-08-30 19:11   ` Jan Engelhardt [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0708302107510.24730@fbirervta.pbzchgretzou.qr \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] Use helpers to obtain task pid in printks (arch code)' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).