From: Christoph Hellwig <hch@infradead.org>
To: Anna Schumaker <Anna.Schumaker@netapp.com>
Cc: Christoph Hellwig <hch@infradead.org>,
trond.myklebust@primarydata.com, linux-nfs@vger.kernel.org
Subject: Re: xfstests generic/285 fails reliably on Trond's linux-next branch
Date: Mon, 1 Aug 2016 06:28:56 -0700 [thread overview]
Message-ID: <20160801132856.GA26191@infradead.org> (raw)
In-Reply-To: <d67d77f3-9df9-4f02-354b-85cc46a5f9c5@Netapp.com>
On Thu, Jul 28, 2016 at 03:36:04PM -0400, Anna Schumaker wrote:
> What mount options are you using? The test passes for me on xfs, btrfs, and ext4.
No mount options at all - just forcing 4.2 with a small patch to
super.c.
I've tried to bisect the issue, but I now see it with Linux 4.7-rc2 as
well. I did upgrade xfstests in the meantime, so I'll see if that
caused the issue, or if it's something that's new in Linux 4.7-rc2 and
Tronds earlier tree was using an older baseline.
prev parent reply other threads:[~2016-08-01 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 8:18 xfstests generic/285 fails reliably on Trond's linux-next branch Christoph Hellwig
2016-07-28 14:46 ` Christoph Hellwig
2016-07-28 19:36 ` Anna Schumaker
2016-08-01 13:28 ` Christoph Hellwig [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=20160801132856.GA26191@infradead.org \
--to=hch@infradead.org \
--cc=Anna.Schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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