From: Al Viro <viro@ZenIV.linux.org.uk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Shawn Starr <shawn.starr@rogers.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [4.7-rc3 June 16th code][EXT4] Rename file corruption?
Date: Wed, 22 Jun 2016 00:20:05 +0100 [thread overview]
Message-ID: <20160621232005.GO14480@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20160616084757.GA15341@infradead.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?
prev parent reply other threads:[~2016-06-22 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 6:27 [4.7-rc3 June 16th code][EXT4] Rename file corruption? Shawn Starr
2016-06-16 8:47 ` Christoph Hellwig
2016-06-21 23:20 ` Al Viro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160621232005.GO14480@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.starr@rogers.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.