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: <20081206084038.GG5957@mail.local.tull.net>
Date:	Sat, 6 Dec 2008 19:40:38 +1100
From:	Nick Andrew <nick@...k-andrew.net>
To:	Joe Perches <joe@...ches.com>
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 Fri, Dec 05, 2008 at 11:42:37PM -0800, Joe Perches wrote:
> I think recursive printk is poor style and
> should be avoided.

I think this is one of those cases where it's a lot harder (or uglier)
to solve a problem non-recursively than it is to solve recursively.

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?

Nick.
--
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/