From: Christoph Hellwig <hch@infradead.org>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: linux-nfs@vger.kernel.org,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v3] pnfs/blocklayout: update last_write_offset atomically with extents
Date: Mon, 19 Sep 2016 07:58:06 -0700 [thread overview]
Message-ID: <20160919145806.GA12452@infradead.org> (raw)
In-Reply-To: <f50699da22fbcd977842a4fa5dd40b27295fcfcf.1471889187.git.bcodding@redhat.com>
So it looks like this patch go in, but when I did my usually NFS
regression tests that I stopped for a few weeks aover the summer it
broke down badly: all the fsx and some other data integrity tests now
fail in xfstests over pNFS blocklayout.
Given how close it is to 4.8-final can we revert it for now?
next prev parent reply other threads:[~2016-09-19 14:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 15:55 [PATCH] pnfs/blocklayout: update last_write_offset atomically with extents Benjamin Coddington
2016-08-18 18:19 ` Trond Myklebust
2016-08-18 18:46 ` Benjamin Coddington
2016-08-22 13:48 ` [PATCH v2] " Benjamin Coddington
2016-08-22 15:34 ` Trond Myklebust
2016-08-22 16:22 ` Benjamin Coddington
2016-08-22 18:11 ` [PATCH v3] " Benjamin Coddington
2016-09-19 14:58 ` Christoph Hellwig [this message]
2016-09-19 19:04 ` Benjamin Coddington
2016-09-19 19:06 ` Christoph Hellwig
2016-09-19 19:40 ` Benjamin Coddington
2016-09-20 12:22 ` [PATCH] pnfs/blocklayout: last_write_offset incorrectly set to end of extent Benjamin Coddington
2016-09-20 16:38 ` Christoph Hellwig
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=20160919145806.GA12452@infradead.org \
--to=hch@infradead.org \
--cc=anna.schumaker@netapp.com \
--cc=bcodding@redhat.com \
--cc=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).