Subject: Re: [RFC] Recursive printk
From: Joe Perches <joe@perches.com>
To: Nick Andrew <nick@nick-andrew.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Linus Torvalds <torvalds@linux-foundation.org>,
       Tejun Heo <tj@kernel.org>, Takashi Iwai <tiwai@suse.de>
In-Reply-To: <20081206084038.GG5957@mail.local.tull.net>
References: <20081206065922.29149.63380.stgit@marcab.local.tull.net>
	 <20081205232016.366765e2.akpm@linux-foundation.org>
	 <1228549357.13046.618.camel@localhost>
	 <20081206084038.GG5957@mail.local.tull.net>
Content-Type: text/plain
Date: Sat, 06 Dec 2008 01:11:33 -0800
Message-Id: <1228554693.13046.624.camel@localhost>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 838
Lines: 20

On Sat, 2008-12-06 at 19:40 +1100, Nick Andrew wrote:
> The basic problem is that subsystems want to prepend or append their
> own data to kernel messages generated by subsystem code, and they
> both want to use printf-type strings. How to combine them into a
> single kernel log message without using extra memory, or double
> handling of strings?

pr_fmt seems to work for that.

I think the question is how to output messages that use
multiple calls to printk so they are not interleaved.

Giving up printf argument verification seems too high a
price to pay for the benefit of recursion.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/