| 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
| ||
|
Date: Mon, 18 Jun 2007 15:53:56 +0200 From: holzheu <holzheu@...ux.vnet.ibm.com> To: Arjan van de Ven <arjan@...radead.org> Cc: Gerrit Huizenga <gh@...ibm.com>, Jan Kara <jack@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, randy.dunlap@...cle.com, gregkh@...e.de, mtk-manpages@....net, schwidefsky@...ibm.com, heiko.carstens@...ibm.com, "lf_kernel_messages@...ux-foundation.org" <lf_kernel_messages@...ux-foundation.org>, pavel@....cz Subject: Re: [RFC/PATCH] Documentation of kernel messages On Mon, 2007-06-18 at 06:12 -0700, Arjan van de Ven wrote: > On Mon, 2007-06-18 at 14:55 +0200, holzheu wrote: > > Hi Gerrit, > > > > The common thing of your and our approach is, that we need an ID to > > identify a message either by: > > > Maybe I am missing something big, but why is an ID needed? > The message IS the ID right? That's the only thing that is robust > against code moving about.... Yes. As already discussed with Pavel, it is one option to use the format string of the message as message ID. The disadvantage compared to message IDs like hashes is, that format strings might be even less unique than hashes and it's probably less convenient for searching by operators. An operator has to issue either: >> info lp.4711 or >> info "lp0: on fire" Michael - 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/
Powered by blists - more mailing lists