linux-kernel - Re: Trailing periods in kernel messages

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: <20071220210741.6dc3caf5@the-village.bc.nu>
Date:	Thu, 20 Dec 2007 21:07:41 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Andy Whitcroft <apw@...dowen.org>
Cc:	Joe Perches <joe@...ches.com>, Li Zefan <lizf@...fujitsu.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frans Pop <elendil@...net.nl>, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, trivial@...nel.org,
	Randy Dunlap <rdunlap@...otime.net>,
	Joel Schopp <jschopp@...tin.ibm.com>
Subject: Re: Trailing periods in kernel messages

> I missed the context on this one.  So this is checking for periods at
> the end of messages for printk's.  We would need something a little
> cleverer to ensure we are only checking the contents of the string.  But
> eminently doable.
> 
> /me plays
> 
> Ok, yes this seems ok.  Have added it for 0.13.

Please remove it.

The kernel printk messages are sentences. English language sentences end
with a full stop. They are messages printed up for normal human beings to
read and they should therefore be properly written.

In fact you should warn if it ends with a newline without a full stop
unless the next line is continuation of quoted text because that suggests
a full stop has been missed out incorrectly.

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