From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Phil Carmody <ext-phil.2.carmody@nokia.com>,
gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3 1/1] sysfs: add more info to the oops dump
Date: Thu, 10 Mar 2011 15:22:01 -0800 [thread overview]
Message-ID: <20110310152201.bb621c3f.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1103110012060.2787@localhost6.localdomain6>
On Fri, 11 Mar 2011 00:13:58 +0100 (CET)
Thomas Gleixner <tglx@linutronix.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.
next prev parent reply other threads:[~2011-03-10 23:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 15:53 [PATCH 1/1] sysfs: add more info to the oops dump Phil Carmody
2011-03-10 16:25 ` Greg KH
2011-03-10 18:32 ` Phil Carmody
2011-03-10 19:02 ` Greg KH
2011-03-10 21:10 ` Phil Carmody
2011-03-10 21:27 ` Greg KH
2011-03-10 22:27 ` [PATCHv3 0/1] " Phil Carmody
2011-03-10 22:27 ` [PATCHv3 1/1] " Phil Carmody
2011-03-10 22:38 ` Andrew Morton
2011-03-10 22:59 ` Thomas Gleixner
2011-03-10 23:03 ` Greg KH
2011-03-10 23:15 ` Andrew Morton
2011-03-10 23:06 ` Phil Carmody
2011-03-10 23:13 ` Thomas Gleixner
2011-03-10 23:22 ` Andrew Morton [this message]
2011-03-10 23:27 ` Thomas Gleixner
2011-03-10 23:46 ` Thomas Gleixner
2011-03-10 23:22 ` Phil Carmody
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110310152201.bb621c3f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ext-phil.2.carmody@nokia.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox