From: Ben Hutchings <ben@decadent.org.uk>
To: Alan Stern <stern@rowland.harvard.edu>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Rocko Requin <rockorequin@hotmail.com>,
tytso@mit.edu,
Kernel development list <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: RE: [Bug 25832] kernel crashes when a mounted ext3/4 file system is physically removed
Date: Mon, 19 Sep 2011 00:00:18 +0100 [thread overview]
Message-ID: <1316386825.14749.207.camel@deadeye> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1109171330360.18455-100000@netrider.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]
On Sat, 2011-09-17 at 13:34 -0400, Alan Stern wrote:
> On Sat, 17 Sep 2011, Rocko Requin wrote:
>
> > > Why were you using gnome-terminal? You should be running the tests at
> > > a console VT, not under X at all. Ctrl-Alt-F2 or the equivalent...
> >
> > Because with Ted's patch it doesn't crash when run from a console VT, even with an X server running.
>
> That's weird. Maybe the screen updates change some timing.
>
> > > Here's another patch to address the new problem. You can apply it on
> > > top of all the other patches.
> >
> > Attached is the crash log I get with the latest patch applied.
>
> Okay, more fallout from the same problem. Here's an updated version of
> the previous patch.
[...]
There have been reports of this in Debian going back to 2.6.39:
http://bugs.debian.org/631187
http://bugs.debian.org/636263
http://bugs.debian.org/642043
Plus possibly related crashes in elv_put_request after CD-ROM removal:
http://bugs.debian.org/633890
http://bugs.debian.org/634681
http://bugs.debian.org/636103
The former was also reported in Ubuntu since their 2.6.38-10:
https://bugs.launchpad.net/debian/+source/linux-2.6/+bug/793796
The result of the discussion there was that it appeared to be a
regression due to commit 86cbfb5607d4b81b1a993ff689bbd2addd5d3a9b
("[SCSI] put stricter guards on queue dead checks") which was also
included in a stable update for 2.6.38.
There was also a report on bugzilla.kernel.org, though no-one can see
quite what that says now:
https://bugzilla.kernel.org/show_bug.cgi?id=38842
I also reported most of the above to James Bottomley and linux-scsi
nearly 2 months ago, to no response.
Ben.
--
Ben Hutchings
Power corrupts. Absolute power is kind of neat.
- John Lehman, Secretary of the US Navy 1981-1987
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next parent reply other threads:[~2011-09-18 23:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY151-W32DCB4BAFEC97DD4913A12A1090@phx.gbl>
[not found] ` <Pine.LNX.4.44L0.1109171330360.18455-100000@netrider.rowland.org>
2011-09-18 23:00 ` Ben Hutchings [this message]
2011-09-20 7:32 ` [Bug 25832] kernel crashes when a mounted ext3/4 file system is physically removed Jun'ichi Nomura
2011-09-22 12:26 ` Hannes Reinecke
2011-09-22 12:35 ` James Bottomley
2011-09-22 15:16 ` Alan Stern
2011-09-22 16:20 ` Thadeu Lima de Souza Cascardo
2011-09-22 16:32 ` Hannes Reinecke
[not found] <BAY151-W13DDCCEFEB7B68EE506214A10C0@phx.gbl>
2011-09-23 15:18 ` Alan Stern
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=1316386825.14749.207.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rockorequin@hotmail.com \
--cc=stern@rowland.harvard.edu \
--cc=tytso@mit.edu \
/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