From: Trond Myklebust <trondmy@primarydata.com>
To: "anna.schumaker@netapp.com" <anna.schumaker@netapp.com>,
"smayhew@redhat.com" <smayhew@redhat.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfs: nfs_commit_inode should redirty inode if the inode has outstanding requests
Date: Fri, 2 Mar 2018 16:52:15 +0000 [thread overview]
Message-ID: <1520009534.6669.3.camel@primarydata.com> (raw)
In-Reply-To: <20180302160038.1598-1-smayhew@redhat.com>
T24gRnJpLCAyMDE4LTAzLTAyIGF0IDExOjAwIC0wNTAwLCBTY290dCBNYXloZXcgd3JvdGU6DQo+
IEl0IHNlZW1zIHRoYXQgbmZzX2NvbW1pdF9pbm9kZSBjYW4gYmUgY2FsbGVkIHdoZXJlIHRoZSBu
ZnNfaW5vZGUgaGFzDQo+IG91dHN0YW5kaW5nIHJlcXVlc3RzIGFuZCB0aGUgY29tbWl0IGxpc3Rz
IGFyZSBlbXB0eS4gIFRoYXQgY2FuIGxlYWQNCj4gdG8NCj4gaW52YWxpZGF0ZV9jb21wbGV0ZV9w
YWdlMiBmYWlsaW5nIGR1ZSB0byB0aGUgYXNzb2NpYXRlZCBwYWdlIGhhdmluZw0KPiBwcml2YXRl
IGRhdGEgd2hpY2ggaW4gdHVybiBsZWFkcyB0byBpbnZhbGlkYXRlX2lub2RlX3BhZ2VzMl9yYW5n
ZQ0KPiByZXR1cm5pbmcgLUVCVVNZLg0KPiANCj4gSW5zdGVhZCBvZiBoYXZpbmcgbmZzX2NvbW1p
dF9pbm9kZSBleGl0IGVhcmx5IHdoZW4gdGhlIGNvbW1pdCBsaXN0cw0KPiBhcmUNCj4gZW1wdHks
IG9ubHkgZG8gc28gaWYgbnJlcXVlc3RzIGlzIGFsc28gMC4NCj4gDQo+IA0KDQpJJ20gbm90IHNl
ZWluZyBob3cgdGhpcyBmYWlsdXJlIHdvdWxkIGhhcHBlbi4gSXMgdGhlcmUgYSBidWcgaW4NCm5m
c19sYXVuZGVyX3BhZ2UoKSBhbmQvb3IgbmZzX3diX3BhZ2UoKT8NCg0KLS0gDQpUcm9uZCBNeWts
ZWJ1c3QNCkxpbnV4IE5GUyBjbGllbnQgbWFpbnRhaW5lciwgUHJpbWFyeURhdGENCnRyb25kLm15
a2xlYnVzdEBwcmltYXJ5ZGF0YS5jb20NCg==
next prev parent reply other threads:[~2018-03-02 16:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 16:00 [PATCH] nfs: nfs_commit_inode should redirty inode if the inode has outstanding requests Scott Mayhew
2018-03-02 16:52 ` Trond Myklebust [this message]
2018-03-02 17:04 ` Trond Myklebust
2018-03-05 21:16 ` J. Bruce Fields
2018-03-05 21:48 ` Trond Myklebust
2018-03-07 19:53 ` Scott Mayhew
2018-03-07 20:38 ` Trond Myklebust
2018-03-08 13:09 ` Scott Mayhew
2018-03-08 17:13 ` Trond Myklebust
2018-03-12 12:07 ` Scott Mayhew
2018-03-12 12:32 ` Trond Myklebust
2018-03-08 21:39 ` bfields
2018-03-08 22:01 ` Trond Myklebust
2018-03-09 2:46 ` bfields
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=1520009534.6669.3.camel@primarydata.com \
--to=trondmy@primarydata.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=smayhew@redhat.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).