From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Duc Dang <dhdang-qTEPVZfXA3Y@public.gmane.org>
Cc: Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>,
"Darrick J. Wong"
<darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
Theodore Ts'o <tytso-3s7WtUTddSA@public.gmane.org>,
Andreas Dilger
<adilger.kernel-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org>,
Jan Kara <jack-IBi9RG/b67k@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
USB list <linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
patches <patches-qTEPVZfXA3Y@public.gmane.org>,
hch-jcswGhMUV9g@public.gmane.org
Subject: Re: 4.2 kernel trace when hot unplug a mounted USB/SATA/MMC devices with ext2/ext3/ext4 file system
Date: Sat, 15 Aug 2015 10:58:10 +0200 [thread overview]
Message-ID: <20150815085810.GA21033@lst.de> (raw)
In-Reply-To: <CADaLNDmXi9ycM8RBLXn69YW-7Z3jw_=iESwn0AODv4VxPymVWw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, Aug 14, 2015 at 05:52:44PM -0700, Duc Dang wrote:
> The commit 08439fec26 "ext4: remove block_device_ejected" only causes
> issue with ext4 and
> trying reverting it helps our test passes with ext4.
>
> But how about the same issue with ext2/ext3?
I tried to fix the underlying issue, but I either failed to fully
fixed it or someone regressed it.
Can you if rev 08439fec26 on it's own works to see if I missed
a case or it was regressed later?
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-08-15 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 3:17 4.2 kernel trace when hot unplug a mounted USB/SATA/MMC devices with ext2/ext3/ext4 file system Duc Dang
[not found] ` <CADaLNDk7NNqe=839ro7KnwpfRAOLO3evX=JL12bMZR8vm2xYMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-13 16:01 ` Darrick J. Wong
[not found] ` <20150813160128.GG10037-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
2015-08-14 8:09 ` Jan Kara
[not found] ` <20150814080932.GA8710-+0h/O2h83AeN3ZZ/Hiejyg@public.gmane.org>
2015-08-15 0:52 ` Duc Dang
[not found] ` <CADaLNDmXi9ycM8RBLXn69YW-7Z3jw_=iESwn0AODv4VxPymVWw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-15 8:58 ` Christoph Hellwig [this message]
[not found] ` <20150815085810.GA21033-jcswGhMUV9g@public.gmane.org>
2015-08-24 21:20 ` Duc Dang
[not found] ` <CADaLNDnupucoQ=7uAEHOfRaEEDZYUORwjC_VcHnBCUfdAoPSdQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-25 8:53 ` Christoph Hellwig
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=20150815085810.GA21033@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=adilger.kernel-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=dhdang-qTEPVZfXA3Y@public.gmane.org \
--cc=jack-AlSwsSmVLrQ@public.gmane.org \
--cc=jack-IBi9RG/b67k@public.gmane.org \
--cc=linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=patches-qTEPVZfXA3Y@public.gmane.org \
--cc=tytso-3s7WtUTddSA@public.gmane.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).