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] [day] [month] [year] [list]
Message-ID: <20150825085314.GA31630@lst.de>
Date:	Tue, 25 Aug 2015 10:53:14 +0200
From:	Christoph Hellwig <hch@....de>
To:	Duc Dang <dhdang@....com>
Cc:	Christoph Hellwig <hch@....de>, 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>
Subject: Re: 4.2 kernel trace when hot unplug a mounted USB/SATA/MMC
	devices with ext2/ext3/ext4 file system

On Mon, Aug 24, 2015 at 02:20:07PM -0700, Duc Dang wrote:
> For more information. We tested kernel at commit 5f80f62ada "ext4:
> remove useless condition in if statement."
> (right before your commit) and still saw the issue.
> 
> df3305156f989339529b3d6744b898d498fb1f7b [media] v4l: xilinx: Add
> Xilinx Video IP core
> 08439fec266c3cc5702953b4f54bdf5649357de0 ext4: remove block_device_ejected
> 5f80f62adae2a2920781a847805d34b36b323f7d ext4: remove useless
> condition in if statement.
> c9bca8b33118573da9b7ac2ea21947a8e4d287dd [media] v4l: of: Add
> v4l2_of_parse_link() function
> 
> Further more, the issue does not happen with 3.19-rc7 but happens with 4.00-rc1

Thanks for the report.  Does it happen with commit aad653
"block: discard bdi_unregister() in favour of bdi_destroy()", either
cherry picked or the whole tree at that version?

--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ