linux-kernel - Re: Top 10 kernel oopses for the week ending January 12th, 2008

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: <20080112233355.GF17276@does.not.exist>
Date:	Sun, 13 Jan 2008 01:33:56 +0200
From:	Adrian Bunk <bunk@...nel.org>
To:	Arjan van de Ven <arjan@...ux.intel.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew.Morton@...a.kernel.org
Subject: Re: Top 10 kernel oopses for the week ending January 12th, 2008

On Sat, Jan 12, 2008 at 03:13:29PM -0800, Arjan van de Ven wrote:
> Adrian Bunk wrote:
>>
>> All the other reports only contain the plain trace. Is there any way to 
>> get more information whether the former is a pattern or not, and to
>> get this information somehow displayed on the webpage?
>
> IF the kernel prints that its tainted or whatever it'll be shown, as well
> as the exact versions etc etc if they are there.
> Sadly none of this information is there prior to 2.6.24-rc4.
>...

OK, the problem might actually not be the omission of displaying the 
tainted information but the omission of considering any relevant 
context.

Looking deeper:

Number #2424 is WARN_ON-after-tainted-oops.

Is your rank 1 just a symptom that the system is in a bad state after 
running in what is your rank 8?

In this case the information when following e.g. #2827 is quite useless 
since wherever you got this trace from all related context information 
like e.g. whether it's like #2424 just the symptom of a previous Oops is 
not displayed.

In the worst case, an entry might only contain WARN_ON traces without 
any information where the traces came from and whether it's worth 
looking at them or whether the system always already was in a known-bad 
state when they occured?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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