linux-kernel - Re: [RFC] Recursive printk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1228554693.13046.624.camel@localhost>
Date:	Sat, 06 Dec 2008 01:11:33 -0800
From:	Joe Perches <joe@...ches.com>
To:	Nick Andrew <nick@...k-andrew.net>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Tejun Heo <tj@...nel.org>, Takashi Iwai <tiwai@...e.de>
Subject: Re: [RFC] Recursive printk

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/