All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Bowler <nbowler@elliptictech.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: possible regression: BUG in client lockd with server reboot.
Date: Mon, 24 Jan 2011 11:54:41 -0500	[thread overview]
Message-ID: <20110124165441.GA14255@elliptictech.com> (raw)
In-Reply-To: <4707872F-6CC4-477D-AE0B-A7DCEEF29ABF@oracle.com>

On 2011-01-24 11:08 -0500, Chuck Lever wrote:
> Nick-
> 
> On Jan 24, 2011, at 9:41 AM, Nick Bowler wrote:
> 
> > We were just having some NFS server troubles, and my client machine
> > running 2.6.38-rc1+ (specifically, commit 2b1caf6ed7b888c95) crashed
> > hard (syslog output appended to this mail).
> 
> I don't seem to have 2b1caf6e.  Can you post the short description?

commit 2b1caf6ed7b888c95a1909d343799672731651a5
Merge: d551d81 bd924e8
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 20 18:30:37 2011 -0800

    Merge branch 'core-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip

> host.c:283 is " BUG_ON(!list_empty(&host->h_lockowners));" in my tree.
> Can you confirm this is the same for you?

Yes, it is.

> I'll have a look.

Great, thanks!

-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

      reply	other threads:[~2011-01-24 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 14:41 possible regression: BUG in client lockd with server reboot Nick Bowler
2011-01-24 16:08 ` Chuck Lever
2011-01-24 16:54   ` Nick Bowler [this message]

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=20110124165441.GA14255@elliptictech.com \
    --to=nbowler@elliptictech.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-kernel@vger.kernel.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.