From: Theodore Ts'o <tytso@mit.edu>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-scsi@vger.kernel.org, linux-ext4@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Bug 101011] Kernel Oops when disconnecting a mounted ext4 usb stick
Date: Fri, 14 Aug 2015 14:39:31 -0400 [thread overview]
Message-ID: <20150814183931.GA3050@thunk.org> (raw)
In-Reply-To: <bug-101011-11613-PGvplgVz20@https.bugzilla.kernel.org/>
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
next prev parent reply other threads:[~2015-08-14 18:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-05 20:17 [Bug 101011] New: Kernel Oops when disconnecting a mounted ext4 usb stick bugzilla-daemon
2015-07-05 20:19 ` [Bug 101011] " bugzilla-daemon
2015-07-05 20:19 ` bugzilla-daemon
2015-07-05 20:20 ` bugzilla-daemon
2015-07-05 20:20 ` bugzilla-daemon
2015-07-22 17:39 ` bugzilla-daemon
2015-08-10 18:02 ` bugzilla-daemon
2015-08-14 11:02 ` bugzilla-daemon
2015-08-14 18:39 ` Theodore Ts'o [this message]
2015-08-15 8:19 ` Christoph Hellwig
2015-08-16 13:38 ` Theodore Ts'o
2015-08-14 18:39 ` bugzilla-daemon
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-13602@https.bugzilla.kernel.org/>
2015-08-10 18:02 ` bugzilla-daemon
2015-08-14 11:02 ` bugzilla-daemon
2015-08-14 18:39 ` bugzilla-daemon
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
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=20150814183931.GA3050@thunk.org \
--to=tytso@mit.edu \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.