linux-kernel - Re: [4.7-rc3 June 16th code][EXT4] Rename file corruption?

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20160621232005.GO14480@ZenIV.linux.org.uk>
Date:	Wed, 22 Jun 2016 00:20:05 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Shawn Starr <shawn.starr@...ers.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org
Subject: Re: [4.7-rc3 June 16th code][EXT4] Rename file corruption?

On Thu, Jun 16, 2016 at 01:47:57AM -0700, Christoph Hellwig wrote:
> We see somewhat similar rename corruption on XFS, also under heavy
> compile workloads.  The reporters have already ruled out the XFS changes
> from the 4.7 merge window, so this looks a lot like the VFS changes
> that went into this merge window.

Can that be triggered on 4e82901 + cherry-pick of e7d6ef979?
Same for 9f541801 + e7d6ef979?