linux-kernel - Re: [patch 1/3] kmsg: Kernel message catalog macros.

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1220272214.23719.9.camel@localhost>
Date:	Mon, 01 Sep 2008 14:30:14 +0200
From:	Martin Schwidefsky <schwidefsky@...ibm.com>
To:	Utz Bacher <utz.bacher@...ibm.com>
Cc:	mschwid2@...ux.vnet.ibm.com,
	Andrew Morton <akpm@...ux-foundation.org>,
	Gerrit Huizenga <gh@...ibm.com>,
	Greg Kroah-Hartman <gregkh@...e.de>, Jan Kara <jack@...e.cz>,
	Jochen Voß <jochen.voss@...glemail.com>,
	Joe Perches <joe@...ches.com>,
	Kunai Takashi <kunai@...ux-foundation.jp>,
	lf_kernel_messages@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org,
	linux-s390-owner@...r.kernel.org,
	Michael Holzheu <holzheu@...ibm.com>,
	Pavel Machek <pavel@....cz>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Sam Ravnborg <sam@...nborg.org>,
	Tim Bird <tim.bird@...sony.com>
Subject: Re: [patch 1/3] kmsg: Kernel message catalog macros.

On Tue, 2008-08-26 at 17:28 +0200, Utz Bacher wrote:
> Martin Schwidefsky wrote on 25.08.2008 17:56:30:
> > If we go with hashes there is one more thing: kmsg(0, <string>)
> > The variant where we manually assign the message ids knows about the
> > "special" id 0. There is no documentation required for id 0 and none is
> > wanted. If we replace the manual ids with hashes this will get lost. You
> > could argue that a kmsg with id 0 is a normal printk so why not just use
> > printk? What is lost is the information that this printk has been found
> > to be not important enough to be documented. 
> 
> what about a kmsg(<string>) and a kmsg_not_for_doc(<string>) with only kmsg 
> being hashed and used for man pages. There might be better names for these 
> functions, though. 

That would double the number of macros we'd have to define. Not really
something I would like to do. Only if there is no other way ..

-- 
blue skies,
  Martin.

"Reality continues to ruin my life." - Calvin.


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