From: Andries Brouwer <aebr@win.tue.nl>
To: Andrew Morton <akpm@zip.com.au>
Cc: Dave Hansen <haveblue@us.ibm.com>,
Badari Pulavarty <pbadari@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at /usr/src/linux-2.5.30/include/linux/dcache.h:261!
Date: Fri, 9 Aug 2002 23:22:31 +0200 [thread overview]
Message-ID: <20020809212231.GB1252@win.tue.nl> (raw)
In-Reply-To: <3D542D75.7FEA9DDF@zip.com.au>
On Fri, Aug 09, 2002 at 02:00:37PM -0700, Andrew Morton wrote:
> > > Code; c0160d0f <d_unhash+f/70> <=====
> It would be much more useful if the oops code were to dump the
> text preceding the exception EIP rather than after it, actually.
I think I already mentioned what the stack trace is for this oops:
for me, it is sd_detach -> driverfs_remove_partitions ->
put_device -> driverfs_remove_dir -> driverfs_rmdir -> d_unhash.
I have seen lots of other oopses related to driverfs.
Submitted a stopgap patch to prevent some of them, but withdrew it
when it became clear that even the ugly stopgap did not prevent all.
This driverfs partition stuff is messy. The code paths where partitions
are created are very different from those where partitions are removed,
and it can easily happen that a partition is removed that was never
created, leading to an oops.
Andries
next prev parent reply other threads:[~2002-08-09 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 17:32 kernel BUG at /usr/src/linux-2.5.30/include/linux/dcache.h:261! Badari Pulavarty
2002-08-09 20:54 ` Dave Hansen
2002-08-09 21:00 ` Andrew Morton
2002-08-09 21:22 ` Andries Brouwer [this message]
2002-08-09 21:47 ` Patrick Mochel
2002-08-10 1:09 ` Keith Owens
2002-08-10 8:08 ` Russell King
2002-08-10 8:44 ` Keith Owens
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=20020809212231.GB1252@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=akpm@zip.com.au \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
/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