linux-kernel - Re: Top 9 kernel oopses/warnings for the week of December 29th, 2007

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071229131712.GB21805@elte.hu>
Date:	Sat, 29 Dec 2007 14:17:12 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Arjan van de Ven <arjan@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	netdev@...r.kernel.org
Subject: Re: Top 9 kernel oopses/warnings for the week of December 29th,
	2007


* Arjan van de Ven <arjan@...ux.intel.com> wrote:

> kerneloops.org news:
>
> * As of 2.6.24-rc6, oopses have a unique identifier which makes it 
>   possible to filter out duplicate reports of (and replies to) the 
>   same oops. Unfortunately some reporters remove this line from their 
>   reports to lkml.

i'd not mind printing out the bootup-ID as a regular part of the oops, 
as long as it's put into an unintrusive place, preferably without adding 
a new line. (just use an empty spot somewhere)

for example:

Call Trace: (ID afbf0104e2079481)
 [<ffffffff805079f6>] sysdev_driver_unregister+0x5b/0x91
 [<ffffffff806f2ef4>] cpufreq_register_driver+0x15a/0x19b
 [<ffffffff80cb0586>] powernowk8_init+0x86/0x94

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