From: Trond Myklebust <trondmy@primarydata.com>
To: "aweits@rit.edu" <aweits@rit.edu>
Cc: "bfields@fieldses.org" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/5] nfsd: Fix stateid races between OPEN and CLOSE
Date: Tue, 31 Oct 2017 23:24:33 +0000 [thread overview]
Message-ID: <1509492271.3397.8.camel@primarydata.com> (raw)
In-Reply-To: <m2vaivrlq2.fsf@discipline.rit.edu>
T24gVHVlLCAyMDE3LTEwLTMxIGF0IDE4OjMzIC0wNDAwLCBBbmRyZXcgVyBFbGJsZSB3cm90ZToN
Cj4gTm90IGRpcmVjdGx5IHJlbGF0ZWQgdG8gdGhpcyBwYXRjaCBzZXJpZXMsIGJ1dDoNCj4gDQo+
IEkga2VlcCBzdGFyaW5nIGF0IHRoZSBmYWlsdXJlIHBhdGggaW4gbmZzZDRfcHJvY2Vzc19vcGVu
MigpIGZyb20gdGhlDQo+IGNhbGwgdG8gbmZzNF9nZXRfdmZzX2ZpbGUoKSBhbmQgdGhpbmtpbmcg
dGhhdCB0aGVyZSdzIGEgbWlzc2luZyBzdGF0ZQ0KPiBjaGFuZ2UgdG8gdGhlIHN0YXRlaWQgdGhh
dCdzIHN0aWxsIGhhc2hlZCBiZWZvcmUgdGhlIG11dGV4IGlzIGRyb3BwZWQNCj4gYW5kIHRoZSBj
YWxsIHRvIHJlbGVhc2Vfb3Blbl9zdGF0ZWlkKCk/DQo+IA0KDQpJZiB0aGUgc2VxaWQ9PTEsIHNv
IHRoYXQgd2Uga25vdyB0aGlzIE9QRU4gb3AgY3JlYXRlZCB0aGF0IHN0YXRlaWQsDQp0aGVuIGl0
IHByb2JhYmx5IHNob3VsZCBiZSB1bmhhc2hlZCBhbmQgbWFya2VkIGFzIGNsb3NlZCwgc2luY2Ug
dGhlbiB3ZQ0Ka25vdyBpdCByZXByZXNlbnRzIG5vIHN0YXRlLiBPdGhlcndpc2UsIEFGQUlDUyBp
dCBzaG91bGQga2VlcCBpdHMNCmN1cnJlbnQgc3RhdGUgKyBzZXFpZC4NCg0KRG8geW91IHdhbnQg
dG8gc2VuZCBhIHBhdGNoLCBvciBzaG91bGQgSSB1cGRhdGUgdGhpcyBwYXRjaCBzZXJpZXM/IFN1
Y2gNCmEgZml4IHByb2JhYmx5IGRvZXMgd2FudCB0byBiZSBhIHN0YWJsZSBwYXRjaCwgc2luY2Ug
aXQgd2lsbCBhZmZlY3QNCmNsaWVudHMgdGhhdCBleHBlY3QgY29tcGxpYW5jZSB3aXRoIFJGQzU2
NjEvUkZDNzUzMC4NCg0KLS0gDQpUcm9uZCBNeWtsZWJ1c3QNCkxpbnV4IE5GUyBjbGllbnQgbWFp
bnRhaW5lciwgUHJpbWFyeURhdGENCnRyb25kLm15a2xlYnVzdEBwcmltYXJ5ZGF0YS5jb20NCg==
next prev parent reply other threads:[~2017-10-31 23:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 0:09 [PATCH 0/5] Tighten up locking around stateids in knfsd Trond Myklebust
2017-10-31 0:09 ` [PATCH 1/5] nfsd: Fix stateid races between OPEN and CLOSE Trond Myklebust
2017-10-31 0:09 ` [PATCH 2/5] nfsd: CLOSE SHOULD return the invalid special stateid for NFSv4.x (x>0) Trond Myklebust
2017-10-31 0:09 ` [PATCH 3/5] nfsd: Ensure we don't recognise lock stateids after freeing them Trond Myklebust
2017-10-31 0:09 ` [PATCH 4/5] nfsd: Ensure we check stateid validity in the seqid operation checks Trond Myklebust
2017-10-31 0:09 ` [PATCH 5/5] nfsd: Fix races with check_stateid_generation() Trond Myklebust
2017-10-31 17:32 ` [PATCH 2/5] nfsd: CLOSE SHOULD return the invalid special stateid for NFSv4.x (x>0) Frank Filz
2017-10-31 22:33 ` [PATCH 1/5] nfsd: Fix stateid races between OPEN and CLOSE Andrew W Elble
2017-10-31 23:24 ` Trond Myklebust [this message]
2017-10-31 23:45 ` Andrew W Elble
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=1509492271.3397.8.camel@primarydata.com \
--to=trondmy@primarydata.com \
--cc=aweits@rit.edu \
--cc=bfields@fieldses.org \
--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.