From: Trond Myklebust <trondmy@primarydata.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"bjschuma@netapp.com" <bjschuma@netapp.com>,
"aglo@umich.edu" <aglo@umich.edu>
Subject: Re: RFC: fixing kernel oops on interrupted COMMIT from nfs_commit_file
Date: Thu, 13 Apr 2017 18:51:25 +0000 [thread overview]
Message-ID: <1492109480.7917.1.camel@primarydata.com> (raw)
In-Reply-To: <CAN-5tyHD9NspwAzL2YwoQGwcUk52ak0OWZ-dBfwpW6nynAf1Og@mail.gmail.com>
T24gVGh1LCAyMDE3LTA0LTEzIGF0IDE0OjAwIC0wNDAwLCBPbGdhIEtvcm5pZXZza2FpYSB3cm90
ZToNCj4gSGkgZm9sa3MsDQo+IA0KPiBMb29raW5nIGZvciBzdWdnZXN0aW9ucyBvbiBob3cgdG8g
Zml4IGEga2VybmVsIG9vcHMuDQo+IA0KPiBJdCdzIHBvc3NpYmxlIHRoYXQgdGhlcmUgaXMgYSBj
dHJsLWMgd2hlbiB0aGUgQ09NTUlUIGlzIHNlbmQuIEluIGNhc2UNCj4gb2YgdGhlIENPUFksIGl0
IGNhbGxzDQo+IG5mc19jb21taXRfZmlsZSgpIHdoaWNoIGNhbGxzIHdhaXRfb25fY29tbWl0KCkg
dGhhdCBpcyBpbnRlcnJ1cHRlZCBieQ0KPiB0aGUgY3J0bC1jIGFuZCBmcmVlcyB0aGUgbmZzX3Bh
Z2UgcmVxdWVzdC4gU28gd2hlbiBhc3luY2hyb25vdXMNCj4gQ09NTUlUDQo+IHJwYyBjb21lcyBi
YWNrIGl0IHRyaWVkIHRvIHVzZSB0aGUgbmZzX3BhZ2UgcmVxdWVzdCBhbmQgZ2V0cyB0aGUNCj4g
b29wcy4NCj4gDQoNCklzIHRoYXQgY2FsbCB0byBuZnNfZnJlZV9yZXF1ZXN0KCkgaW4gbmZzX2Nv
bW1pdF9maWxlKCkgY29ycmVjdD8gSXQNCmxvb2tzIHRvIG1lIGFzIGlmIHRoZSBzYW1lIHJlcXVl
c3Qgd2lsbCBiZSBmcmVlZCBpbg0KbmZzX2NvbW1pdF9yZWxlYXNlX3BhZ2VzKCkuDQoNCkFubmE/
DQoNCi0tIA0KVHJvbmQgTXlrbGVidXN0DQpMaW51eCBORlMgY2xpZW50IG1haW50YWluZXIsIFBy
aW1hcnlEYXRhDQp0cm9uZC5teWtsZWJ1c3RAcHJpbWFyeWRhdGEuY29tDQo=
next prev parent reply other threads:[~2017-04-13 18:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 18:00 RFC: fixing kernel oops on interrupted COMMIT from nfs_commit_file Olga Kornievskaia
2017-04-13 18:51 ` Trond Myklebust [this message]
2017-04-13 19:07 ` Olga Kornievskaia
2017-04-13 19:16 ` Anna Schumaker
2017-04-13 20:13 ` Anna Schumaker
2017-04-13 20:38 ` Olga Kornievskaia
2017-04-13 20:50 ` Trond Myklebust
2017-04-14 15:56 ` Olga Kornievskaia
2017-04-14 16:04 ` [PATCH 1/1] NFS " Olga Kornievskaia
2017-04-14 19:16 ` RFC: " Trond Myklebust
2017-04-14 21:17 ` Olga Kornievskaia
2017-04-17 21:17 ` Olga Kornievskaia
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=1492109480.7917.1.camel@primarydata.com \
--to=trondmy@primarydata.com \
--cc=aglo@umich.edu \
--cc=bjschuma@netapp.com \
--cc=linux-nfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.