linux-ext4 - Re: 4.2 kernel trace when hot unplug a mounted USB/SATA/MMC devices with ext2/ext3/ext4 file system

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 15 Aug 2015 10:58:10 +0200
From:	Christoph Hellwig <hch@....de>
To:	Duc Dang <dhdang@....com>
Cc:	Jan Kara <jack@...e.cz>,
	"Darrick J. Wong" <darrick.wong@...cle.com>,
	Theodore Ts'o <tytso@....edu>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	Jan Kara <jack@...e.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-ext4@...r.kernel.org, USB list <linux-usb@...r.kernel.org>,
	patches <patches@....com>, hch@....de
Subject: Re: 4.2 kernel trace when hot unplug a mounted USB/SATA/MMC
	devices with ext2/ext3/ext4 file system

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-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html