2012-03-02 13:32:57

by Mkrtchyan, Tigran

[permalink] [raw]
Subject: invalid sequence id

According rfc5661 section 2.10..6.1:


The first time a slot is used, the requester MUST specify a sequence
ID of one.

Nevertheless, current client (git://linux-nfs.org/~trondmy/nfs-2.6.git
abd96698613eb27415e7028b6100be930920adc6)

sends starts with zero:


fedora kernel 3.2.7 does it correct.


Regards,
Tigran.


2012-03-02 13:39:43

by Myklebust, Trond

[permalink] [raw]
Subject: Re: invalid sequence id

T24gRnJpLCAyMDEyLTAzLTAyIGF0IDE0OjMyICswMTAwLCBUaWdyYW4gTWtydGNoeWFuIHdyb3Rl
Og0KPiBBY2NvcmRpbmcgcmZjNTY2MSBzZWN0aW9uIDIuMTAuLjYuMToNCj4gDQo+IA0KPiAgVGhl
IGZpcnN0IHRpbWUgYSBzbG90IGlzIHVzZWQsIHRoZSByZXF1ZXN0ZXIgTVVTVCBzcGVjaWZ5IGEg
IHNlcXVlbmNlDQo+IElEIG9mIG9uZS4NCj4gDQo+IE5ldmVydGhlbGVzcywgY3VycmVudCBjbGll
bnQgKGdpdDovL2xpbnV4LW5mcy5vcmcvfnRyb25kbXkvbmZzLTIuNi5naXQNCj4gYWJkOTY2OTg2
MTNlYjI3NDE1ZTcwMjhiNjEwMGJlOTMwOTIwYWRjNikNCj4gDQo+IHNlbmRzIHN0YXJ0cyB3aXRo
IHplcm86DQo+IA0KPiANCj4gZmVkb3JhIGtlcm5lbCAzLjIuNyBkb2VzIGl0IGNvcnJlY3QuDQoN
ClRoYXQgaXNzdWUgaXMgZml4ZWQgaW4gdXBzdHJlYW0uIEkgd2lsbCBiYWNrLW1lcmdlIHRvIHRo
ZSBuZnMtZm9yLW5leHQNCnNvb24sIGluIHRoZSBtZWFudGltZSwgdHJ5IHVzaW5nIHRoZSBsaW51
eC1uZXh0IGJyYW5jaCB3aGljaCBhbHJlYWR5IGhhcw0KYSBiYWNrLW1lcmdlIG9mIHRoZSBmaXgu
DQoNCkNoZWVycw0KICBUcm9uZA0KLS0gDQpUcm9uZCBNeWtsZWJ1c3QNCkxpbnV4IE5GUyBjbGll
bnQgbWFpbnRhaW5lcg0KDQpOZXRBcHANClRyb25kLk15a2xlYnVzdEBuZXRhcHAuY29tDQp3d3cu
bmV0YXBwLmNvbQ0KDQo=

2012-03-02 13:41:36

by Mkrtchyan, Tigran

[permalink] [raw]
Subject: Re: invalid sequence id

Thanks.

On Fri, Mar 2, 2012 at 2:39 PM, Myklebust, Trond
<[email protected]> wrote:
> On Fri, 2012-03-02 at 14:32 +0100, Tigran Mkrtchyan wrote:
>> According rfc5661 section 2.10..6.1:
>>
>>
>>  The first time a slot is used, the requester MUST specify a  sequence
>> ID of one.
>>
>> Nevertheless, current client (git://linux-nfs.org/~trondmy/nfs-2.6.git
>> abd96698613eb27415e7028b6100be930920adc6)
>>
>> sends starts with zero:
>>
>>
>> fedora kernel 3.2.7 does it correct.
>
> That issue is fixed in upstream. I will back-merge to the nfs-for-next
> soon, in the meantime, try using the linux-next branch which already has
> a back-merge of the fix.
>
> Cheers
>  Trond
> --
> Trond Myklebust
> Linux NFS client maintainer
>
> NetApp
> [email protected]
> http://www.netapp.com
>