Re: krb5 failures in recent nfs-for-next

["J. Bruce Fields" <bfields@fieldses.org>]

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.