From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751844AbcFVAJd (ORCPT ); Tue, 21 Jun 2016 20:09:33 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:44472 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750907AbcFVAJb (ORCPT ); Tue, 21 Jun 2016 20:09:31 -0400 Date: Wed, 22 Jun 2016 00:20:05 +0100 From: Al Viro To: Christoph Hellwig Cc: Shawn Starr , Linux Kernel list , linux-fsdevel@vger.kernel.org Subject: Re: [4.7-rc3 June 16th code][EXT4] Rename file corruption? Message-ID: <20160621232005.GO14480@ZenIV.linux.org.uk> References: <2928286.B1kamKfYiW@segfault> <20160616084757.GA15341@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160616084757.GA15341@infradead.org> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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?