linux-kernel - Re: [PATCH] Use vprintk rather that vsnprintf where possible

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: <1228450905.13046.51.camel@localhost>
Date:	Thu, 04 Dec 2008 20:21:45 -0800
From:	Joe Perches <joe@...ches.com>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Matt Mackall <mpm@...enic.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Use vprintk rather that vsnprintf where possible

On Fri, 2008-12-05 at 04:05 +0100, Kay Sievers wrote:
> If we convert to two printk calls for a single line, does that not
> possibly get mixed up with printks from other locations and lead to
> hardly readable log output?

Yes it does.

There are hundreds of possible interleaves in kernel
source today.  Adding a couple more isn't horrible.

The changes Matt proposes are good because they make the
kernel image smaller with a very minimal chance of
deciphering difficulty.

Someday there'll be a "multiline_printk_start/end"
mechanism that will avoid interleaving.

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