linux-kernel - Re: [RFC/PATCH] Update coding standard to avoid ungrepable printk format strings

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: <20080222140142.GA23221@one.firstfloor.org>
Date:	Fri, 22 Feb 2008 15:01:42 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	torvalds@...l.org
Subject: Re: [RFC/PATCH] Update coding standard to avoid ungrepable printk format strings

> Instead of a new recommendation (from now on we recommend something
> contrary to what we required up until yesterday --- let's go unwrap
> strings everywhere in the kernel now), how about simply saying that
> printk format strings are not subject to the 80 column rule?

I personally slightly prefer the "unindent" solution over the ">80char"
solution, but it is not a very strong preference and both would be ok
for me.

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