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]
Date:	Sun, 13 Jan 2008 00:23:22 +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 10:48:05AM -0800, Arjan van de Ven wrote:
> The http://www.kerneloops.org website collects kernel oops and
> warning reports from various mailing lists and bugzillas as well as
> with a client users can install to auto-submit oopses.
> Below is a top 10 list of the oopses collected in the last 7 days.
> (Reports prior to 2.6.23 have been omitted in collecting the top 10)
>
> This week, a total of 136 oopses and warnings have been reported,
> compared to 46 reports in the previous 7 days.
>
> kerneloops.org news:
> 	* Based on feedback from last weeks report, the website now tries
> 	  to also present a disassembled Code: line
> 	* the kerneloops collection client is now part of Fedora (rawhide)
> 	  (yum install kerneloops)
> 	* the kerneloops collection client is now included in Debian testing
> 	  (apt-get install kerneloops)
> 	* gentoo has received an updated version of the client
>
>
> Rank 1: implement (hid code)
> 	WARN_ON at drivers/hid/hid-core.c:784
> 	Reported 23 times (39 total reports)
> 	This appears to be the kernel doing a WARN_ON based on unexpected ioctl() arguments
> 	More info: http://www.kerneloops.org/search.php?search=implement
>...

The only complete bug reports seems to be from one user who loaded a 
module whose distribution might be considered a criminal act in some 
countries.

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?

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ