krb5 failures in recent nfs-for-next

krb5 failures in recent nfs-for-next

[J. Bruce Fields]

Have you been doing any krb5 testing?

I'm seeing the client crash as of nfs-for-next, and haven't been able to
get any debugging out of it so far.

--b.

Re: krb5 failures in recent nfs-for-next

[Bryan Schumaker]

On 03/21/2012 03:24 PM, J. Bruce Fields wrote:

> Have you been doing any krb5 testing?


Not yet.  It's still on my Jenkins todo list, but I haven't gotten around to it yet.  Sounds like we need it, though, so I'll try working on it soon.

- Bryan

> 
> I'm seeing the client crash as of nfs-for-next, and haven't been able to
> get any debugging out of it so far.
> 
> --b.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: krb5 failures in recent nfs-for-next

[J. Bruce Fields]

On Wed, Mar 21, 2012 at 03:37:12PM -0400, Bryan Schumaker wrote:
> On 03/21/2012 03:24 PM, J. Bruce Fields wrote:
> 
> > Have you been doing any krb5 testing?
> 
> 
> Not yet.  It's still on my Jenkins todo list, but I haven't gotten around to it yet.  Sounds like we need it, though, so I'll try working on it soon.

Actually, I've since seen the failure over nfsv4 and auth_sys.  All
that's left on the console is enough to tell me it's happening in
nfs4_free_lock_state, called from __rpc_execute in a kthread.  (Well,
assuming that's actually the first backtrace.)

--b.

Re: krb5 failures in recent nfs-for-next

[Adamson, Dros]

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

Hey Bruce,

Any more info on this?  nfs-for-next wfm with kerberos against a server with fedora 16 kernel 3.2.10-3.fc16.x86_64.

-dros

On Mar 21, 2012, at 3:45 PM, J. Bruce Fields wrote:

> On Wed, Mar 21, 2012 at 03:37:12PM -0400, Bryan Schumaker wrote:
>> On 03/21/2012 03:24 PM, J. Bruce Fields wrote:
>> 
>>> Have you been doing any krb5 testing?
>> 
>> 
>> Not yet.  It's still on my Jenkins todo list, but I haven't gotten around to it yet.  Sounds like we need it, though, so I'll try working on it soon.
> 
> Actually, I've since seen the failure over nfsv4 and auth_sys.  All
> that's left on the console is enough to tell me it's happening in
> nfs4_free_lock_state, called from __rpc_execute in a kthread.  (Well,
> assuming that's actually the first backtrace.)
> 
> --b.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 1374 bytes --]

Re: krb5 failures in recent nfs-for-next

[Myklebust, Trond]

T24gV2VkLCAyMDEyLTAzLTIxIGF0IDE1OjQ1IC0wNDAwLCBKLiBCcnVjZSBGaWVsZHMgd3JvdGU6
DQo+IE9uIFdlZCwgTWFyIDIxLCAyMDEyIGF0IDAzOjM3OjEyUE0gLTA0MDAsIEJyeWFuIFNjaHVt
YWtlciB3cm90ZToNCj4gPiBPbiAwMy8yMS8yMDEyIDAzOjI0IFBNLCBKLiBCcnVjZSBGaWVsZHMg
d3JvdGU6DQo+ID4gDQo+ID4gPiBIYXZlIHlvdSBiZWVuIGRvaW5nIGFueSBrcmI1IHRlc3Rpbmc/
DQo+ID4gDQo+ID4gDQo+ID4gTm90IHlldC4gIEl0J3Mgc3RpbGwgb24gbXkgSmVua2lucyB0b2Rv
IGxpc3QsIGJ1dCBJIGhhdmVuJ3QgZ290dGVuIGFyb3VuZCB0byBpdCB5ZXQuICBTb3VuZHMgbGlr
ZSB3ZSBuZWVkIGl0LCB0aG91Z2gsIHNvIEknbGwgdHJ5IHdvcmtpbmcgb24gaXQgc29vbi4NCj4g
DQo+IEFjdHVhbGx5LCBJJ3ZlIHNpbmNlIHNlZW4gdGhlIGZhaWx1cmUgb3ZlciBuZnN2NCBhbmQg
YXV0aF9zeXMuICBBbGwNCj4gdGhhdCdzIGxlZnQgb24gdGhlIGNvbnNvbGUgaXMgZW5vdWdoIHRv
IHRlbGwgbWUgaXQncyBoYXBwZW5pbmcgaW4NCj4gbmZzNF9mcmVlX2xvY2tfc3RhdGUsIGNhbGxl
ZCBmcm9tIF9fcnBjX2V4ZWN1dGUgaW4gYSBrdGhyZWFkLiAgKFdlbGwsDQo+IGFzc3VtaW5nIHRo
YXQncyBhY3R1YWxseSB0aGUgZmlyc3QgYmFja3RyYWNlLikNCg0KSSd2ZSBqdXN0IGJlZW4gc2xv
dyB0byB1cGRhdGUgbmZzLWZvci1uZXh0LiBUaGVyZSBoYXMgYmVlbiBhIGZpeCBmb3INCnRoaXMg
aW4gdGhlICdkZXZlbCcgYW5kICdsaW51eC1uZXh0JyBicmFuY2hlcyBmb3IgYSB3aGlsZS4gUHVz
aGVkIG91dA0Kbm93Li4uDQoNClRoZSBhY3R1YWwgY29tbWl0ZGlmZiBpcyBoZXJlOg0KICBodHRw
Oi8vZ2l0LmxpbnV4LW5mcy5vcmcvP3A9dHJvbmRteS9saW51eC1uZnMuZ2l0O2E9Y29tbWl0ZGlm
ZjtoPTVhZTY3YzRmZWU4NjljOWIzYzg3YjcyN2E5ZWE1MTFiNjMyNmI4MzQNCg0KLS0gDQpUcm9u
ZCBNeWtsZWJ1c3QNCkxpbnV4IE5GUyBjbGllbnQgbWFpbnRhaW5lcg0KDQpOZXRBcHANClRyb25k
Lk15a2xlYnVzdEBuZXRhcHAuY29tDQp3d3cubmV0YXBwLmNvbQ0KDQo=

Re: krb5 failures in recent nfs-for-next

[J. Bruce Fields]

On Wed, Mar 21, 2012 at 07:57:03PM +0000, Myklebust, Trond wrote:
> On Wed, 2012-03-21 at 15:45 -0400, J. Bruce Fields wrote:
> > On Wed, Mar 21, 2012 at 03:37:12PM -0400, Bryan Schumaker wrote:
> > > On 03/21/2012 03:24 PM, J. Bruce Fields wrote:
> > > 
> > > > Have you been doing any krb5 testing?
> > > 
> > > 
> > > Not yet.  It's still on my Jenkins todo list, but I haven't gotten around to it yet.  Sounds like we need it, though, so I'll try working on it soon.
> > 
> > Actually, I've since seen the failure over nfsv4 and auth_sys.  All
> > that's left on the console is enough to tell me it's happening in
> > nfs4_free_lock_state, called from __rpc_execute in a kthread.  (Well,
> > assuming that's actually the first backtrace.)
> 
> I've just been slow to update nfs-for-next. There has been a fix for
> this in the 'devel' and 'linux-next' branches for a while. Pushed out
> now...
> 
> The actual commitdiff is here:
>   http://git.linux-nfs.org/?p=trondmy/linux-nfs.git;a=commitdiff;h=5ae67c4fee869c9b3c87b727a9ea511b6326b834

Thanks!

And that tree's stable, right?

In which case if you've no objection I'll likely merge it with a note
that I need it (well, some of the container changes) for jlayton's
reboot recovery patches.

--b.

Re: krb5 failures in recent nfs-for-next

[Myklebust, Trond]

T24gV2VkLCAyMDEyLTAzLTIxIGF0IDE2OjUwIC0wNDAwLCBKLiBCcnVjZSBGaWVsZHMgd3JvdGU6
DQo+IE9uIFdlZCwgTWFyIDIxLCAyMDEyIGF0IDA3OjU3OjAzUE0gKzAwMDAsIE15a2xlYnVzdCwg
VHJvbmQgd3JvdGU6DQo+ID4gT24gV2VkLCAyMDEyLTAzLTIxIGF0IDE1OjQ1IC0wNDAwLCBKLiBC
cnVjZSBGaWVsZHMgd3JvdGU6DQo+ID4gPiBPbiBXZWQsIE1hciAyMSwgMjAxMiBhdCAwMzozNzox
MlBNIC0wNDAwLCBCcnlhbiBTY2h1bWFrZXIgd3JvdGU6DQo+ID4gPiA+IE9uIDAzLzIxLzIwMTIg
MDM6MjQgUE0sIEouIEJydWNlIEZpZWxkcyB3cm90ZToNCj4gPiA+ID4gDQo+ID4gPiA+ID4gSGF2
ZSB5b3UgYmVlbiBkb2luZyBhbnkga3JiNSB0ZXN0aW5nPw0KPiA+ID4gPiANCj4gPiA+ID4gDQo+
ID4gPiA+IE5vdCB5ZXQuICBJdCdzIHN0aWxsIG9uIG15IEplbmtpbnMgdG9kbyBsaXN0LCBidXQg
SSBoYXZlbid0IGdvdHRlbiBhcm91bmQgdG8gaXQgeWV0LiAgU291bmRzIGxpa2Ugd2UgbmVlZCBp
dCwgdGhvdWdoLCBzbyBJJ2xsIHRyeSB3b3JraW5nIG9uIGl0IHNvb24uDQo+ID4gPiANCj4gPiA+
IEFjdHVhbGx5LCBJJ3ZlIHNpbmNlIHNlZW4gdGhlIGZhaWx1cmUgb3ZlciBuZnN2NCBhbmQgYXV0
aF9zeXMuICBBbGwNCj4gPiA+IHRoYXQncyBsZWZ0IG9uIHRoZSBjb25zb2xlIGlzIGVub3VnaCB0
byB0ZWxsIG1lIGl0J3MgaGFwcGVuaW5nIGluDQo+ID4gPiBuZnM0X2ZyZWVfbG9ja19zdGF0ZSwg
Y2FsbGVkIGZyb20gX19ycGNfZXhlY3V0ZSBpbiBhIGt0aHJlYWQuICAoV2VsbCwNCj4gPiA+IGFz
c3VtaW5nIHRoYXQncyBhY3R1YWxseSB0aGUgZmlyc3QgYmFja3RyYWNlLikNCj4gPiANCj4gPiBJ
J3ZlIGp1c3QgYmVlbiBzbG93IHRvIHVwZGF0ZSBuZnMtZm9yLW5leHQuIFRoZXJlIGhhcyBiZWVu
IGEgZml4IGZvcg0KPiA+IHRoaXMgaW4gdGhlICdkZXZlbCcgYW5kICdsaW51eC1uZXh0JyBicmFu
Y2hlcyBmb3IgYSB3aGlsZS4gUHVzaGVkIG91dA0KPiA+IG5vdy4uLg0KPiA+IA0KPiA+IFRoZSBh
Y3R1YWwgY29tbWl0ZGlmZiBpcyBoZXJlOg0KPiA+ICAgaHR0cDovL2dpdC5saW51eC1uZnMub3Jn
Lz9wPXRyb25kbXkvbGludXgtbmZzLmdpdDthPWNvbW1pdGRpZmY7aD01YWU2N2M0ZmVlODY5Yzli
M2M4N2I3MjdhOWVhNTExYjYzMjZiODM0DQo+IA0KPiBUaGFua3MhDQo+IA0KPiBBbmQgdGhhdCB0
cmVlJ3Mgc3RhYmxlLCByaWdodD8NCg0KWWVzLiBUaGF0J3Mgd2h5IEkgd2FzIHNsb3cgdG8gbWVy
Z2U6IEkgd2FudGVkIGFtcGxlIHRlc3RpbmcgZmlyc3QuDQoNCj4gSW4gd2hpY2ggY2FzZSBpZiB5
b3UndmUgbm8gb2JqZWN0aW9uIEknbGwgbGlrZWx5IG1lcmdlIGl0IHdpdGggYSBub3RlDQo+IHRo
YXQgSSBuZWVkIGl0ICh3ZWxsLCBzb21lIG9mIHRoZSBjb250YWluZXIgY2hhbmdlcykgZm9yIGps
YXl0b24ncw0KPiByZWJvb3QgcmVjb3ZlcnkgcGF0Y2hlcy4NCg0KT0suIEknbGwgbGlrZWx5IGJl
IHNlbmRpbmcgdGhlIG1lcmdlIHJlcXVlc3QgdG8gTGludXMgb24gb3IgYmVmb3JlDQpGcmlkYXku
DQoNCi0tIA0KVHJvbmQgTXlrbGVidXN0DQpMaW51eCBORlMgY2xpZW50IG1haW50YWluZXINCg0K
TmV0QXBwDQpUcm9uZC5NeWtsZWJ1c3RAbmV0YXBwLmNvbQ0Kd3d3Lm5ldGFwcC5jb20NCg0K

Re: krb5 failures in recent nfs-for-next

[J. Bruce Fields]

On Wed, Mar 21, 2012 at 08:53:45PM +0000, Myklebust, Trond wrote:
> On Wed, 2012-03-21 at 16:50 -0400, J. Bruce Fields wrote:
> > On Wed, Mar 21, 2012 at 07:57:03PM +0000, Myklebust, Trond wrote:
> > > On Wed, 2012-03-21 at 15:45 -0400, J. Bruce Fields wrote:
> > > > On Wed, Mar 21, 2012 at 03:37:12PM -0400, Bryan Schumaker wrote:
> > > > > On 03/21/2012 03:24 PM, J. Bruce Fields wrote:
> > > > > 
> > > > > > Have you been doing any krb5 testing?
> > > > > 
> > > > > 
> > > > > Not yet.  It's still on my Jenkins todo list, but I haven't gotten around to it yet.  Sounds like we need it, though, so I'll try working on it soon.
> > > > 
> > > > Actually, I've since seen the failure over nfsv4 and auth_sys.  All
> > > > that's left on the console is enough to tell me it's happening in
> > > > nfs4_free_lock_state, called from __rpc_execute in a kthread.  (Well,
> > > > assuming that's actually the first backtrace.)
> > > 
> > > I've just been slow to update nfs-for-next. There has been a fix for
> > > this in the 'devel' and 'linux-next' branches for a while. Pushed out
> > > now...
> > > 
> > > The actual commitdiff is here:
> > >   http://git.linux-nfs.org/?p=trondmy/linux-nfs.git;a=commitdiff;h=5ae67c4fee869c9b3c87b727a9ea511b6326b834
> > 
> > Thanks!
> > 
> > And that tree's stable, right?
> 
> Yes. That's why I was slow to merge: I wanted ample testing first.
> 
> > In which case if you've no objection I'll likely merge it with a note
> > that I need it (well, some of the container changes) for jlayton's
> > reboot recovery patches.
> 
> OK. I'll likely be sending the merge request to Linus on or before
> Friday.

That'll work.  I'm running slower than that.

Thanks!  (Tests pass now.)

--b.