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

From: Andrew Morton
Date: Thu Mar 10 2011 - 18:22:17 EST


On Fri, 11 Mar 2011 00:13:58 +0100 (CET)
Thomas Gleixner <tglx@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/