From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from bombadil.infradead.org ([198.137.202.9]:35764 "EHLO
	bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751276AbcFPIr6 (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Thu, 16 Jun 2016 04:47:58 -0400
Date: Thu, 16 Jun 2016 01:47:57 -0700
From: Christoph Hellwig <hch@infradead.org>
To: Shawn Starr <shawn.starr@rogers.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: Re: [4.7-rc3 June 16th code][EXT4] Rename file corruption?
Message-ID: <20160616084757.GA15341@infradead.org>
References: <2928286.B1kamKfYiW@segfault>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2928286.B1kamKfYiW@segfault>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

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.