From: Christoph Hellwig <hch@infradead.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: Reported regressions for 4.7 as of Sunday, 2016-06-19
Date: Mon, 20 Jun 2016 03:21:22 -0700 [thread overview]
Message-ID: <20160620102122.GB23462@infradead.org> (raw)
In-Reply-To: <7cc588b7-f1cf-62a8-e45b-ec7d863ba51e@leemhuis.info>
Another important one is the rename regression in XFS and ext4 that
I suspect is due the VFS changes in 4.7:
http://oss.sgi.com/pipermail/xfs/2016-June/049138.html
http://oss.sgi.com/pipermail/xfs/2016-June/049309.html
possibly related:
http://marc.info/?l=linux-kernel&m=146605889024559&w=2
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
parent reply other threads:[~2016-06-20 10:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <7cc588b7-f1cf-62a8-e45b-ec7d863ba51e@leemhuis.info>]
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=20160620102122.GB23462@infradead.org \
--to=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=torvalds@linux-foundation.org \
--cc=xfs@oss.sgi.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 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).