From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 101011] Kernel Oops when disconnecting a mounted ext4 usb stick
Date: Fri, 14 Aug 2015 18:39:43 +0000 [thread overview]
Message-ID: <bug-101011-13602-HVW753rY8L@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-101011-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=101011
--- Comment #8 from Theodore Tso <tytso@mit.edu> ---
On Fri, Aug 14, 2015 at 11:02:14AM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=101011
>
> I can also confirm that this bug is present in latest stable kernel (4.1.5) and
> reverting commit from comment 6 seems to fix it.
Christoph,
I've since gotten two reports from users that reverting your commit:
"08439fec266c3: ext4: remove block_device_ejected" fixes a crash when
a USB stick is yanked from their system. Looking at the reported
stack dump, it looks like the crash is happening in
account_page_dirtied() when it updates some bdi-specific statistics.
I haven't been paying attention to the recent changes in how bdi gets
torn down after the device gets removed, and in fact finding the
recent changes wasn't obvioius enough after doing a brief search, but
it seems to me that if reverting this patch is making any kind of
differences, then the assertion in the commit description:
bdi->dev now never goes away, so this function became useless.
it implies that bdi->dev *does* become NULL, and checking for this is
useful. In any case, I don't see any harm in reverting this commit;
what do you think?
Thanks,
- Ted
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-08-14 18:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-101011-13602@https.bugzilla.kernel.org/>
2015-08-10 18:02 ` [Bug 101011] Kernel Oops when disconnecting a mounted ext4 usb stick bugzilla-daemon
2015-08-14 11:02 ` bugzilla-daemon
2015-08-14 18:39 ` bugzilla-daemon [this message]
2015-08-15 8:19 ` bugzilla-daemon
2015-08-16 13:38 ` bugzilla-daemon
2015-09-28 18:49 ` bugzilla-daemon
2015-09-28 21:46 ` bugzilla-daemon
2015-09-28 21:47 ` bugzilla-daemon
2015-09-29 16:33 ` bugzilla-daemon
[not found] <bug-101011-11613@https.bugzilla.kernel.org/>
[not found] ` <bug-101011-11613-PGvplgVz20@https.bugzilla.kernel.org/>
2015-08-14 18:39 ` Theodore Ts'o
2015-08-15 8:19 ` Christoph Hellwig
2015-08-16 13:38 ` Theodore Ts'o
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=bug-101011-13602-HVW753rY8L@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).