linux-kernel - Re: [PATCHv3 1/1] sysfs: add more info to the oops dump

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:	Thu, 10 Mar 2011 15:22:01 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Phil Carmody <ext-phil.2.carmody@...ia.com>, gregkh@...e.de,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCHv3 1/1] sysfs: add more info to the oops dump

On Fri, 11 Mar 2011 00:13:58 +0100 (CET)
Thomas Gleixner <tglx@...utronix.de> wrote:

> > > It's more of an distraction than anything which is relevant to 99.999%
> > > of the problems we have to deal with.
> > 
> > As I indicated before, I've previously thought that too, but thought I
> > could 'fix' it by adding to it when I hit the once-in-three-years case.
> 
> The interesting question is:
> 
>  How did that info help and was it really the ultimate reason why you
>  found the underlying bug ?

What happens with sysfs is that if a subsystem's handler is buggy, that
tends to cause a crash within sysfs core code.  You get a stack trace
which contains only VFS and sysfs functions - there is no symbol in the
trace which permits you to identify the offending subsystem.
--
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/