On Sunday 17 August 2008 06:40:50 Tim Hockin wrote: > On Sat, Aug 16, 2008 at 10:49 AM, Martin Schwidefsky > > <schwidefsky@xxxxxxxxxx> wrote: > >> > > Can you hash the format string to generate the id? 6 hex digits > >> > > should be enough, and your tool can check for clashes. As it's bad > >> > > form to have identical strings for different semantics anyway, this > >> > > seems to make sense. > > > > Ok, so a specialized version of printk will do the work to calculate > > the hash. Only, what will we do if there ever is a conflict? The message > > tag has to be unique. The shorter the hash is, the more likely a > > collision gets. Don't know if 6 hash digits is enough to just ignore the > > problem. > > And if you ever need to change the text that is in the format string? > The hash changes. That seems exactly counter to your goal... You need to catalogue them all anyway, so you can detect clashes at build time. Yes, you have to change the new string in that case, but that's easy. And the number changing as the message changes is arguably a feature. You shouldn't (and we generally don't) idly change kernel messages. Rusty. -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
