* Re: [4.7-rc3 June 16th code][EXT4] Rename file corruption?
[not found] <2928286.B1kamKfYiW@segfault>
@ 2016-06-16 8:47 ` Christoph Hellwig
2016-06-21 23:20 ` Al Viro
0 siblings, 1 reply; 2+ messages in thread
From: Christoph Hellwig @ 2016-06-16 8:47 UTC (permalink / raw)
To: Shawn Starr; +Cc: Linux Kernel list, viro, linux-fsdevel
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [4.7-rc3 June 16th code][EXT4] Rename file corruption?
2016-06-16 8:47 ` [4.7-rc3 June 16th code][EXT4] Rename file corruption? Christoph Hellwig
@ 2016-06-21 23:20 ` Al Viro
0 siblings, 0 replies; 2+ messages in thread
From: Al Viro @ 2016-06-21 23:20 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: Shawn Starr, Linux Kernel list, linux-fsdevel
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?
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-06-22 0:09 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <2928286.B1kamKfYiW@segfault>
2016-06-16 8:47 ` [4.7-rc3 June 16th code][EXT4] Rename file corruption? Christoph Hellwig
2016-06-21 23:20 ` Al Viro
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).