From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Adrian Bunk" <bunk@stusta.de>
Cc: "Trond Myklebust" <trond.myklebust@fys.uio.no>,
"Fermin Molina" <fermin@asic.udl.es>,
linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at fs/locks.c:1932!
Date: Sat, 25 Feb 2006 16:46:30 +0100 [thread overview]
Message-ID: <9a8748490602250746m30745f30sfe989ff4b2a1ecf2@mail.gmail.com> (raw)
In-Reply-To: <20060225153525.GT3674@stusta.de>
On 2/25/06, Adrian Bunk <bunk@stusta.de> wrote:
> On Sun, Feb 19, 2006 at 01:27:55PM -0500, Trond Myklebust wrote:
> > On Fri, 2006-02-17 at 16:15 +0100, Fermin Molina wrote:
> > > Hi,
> > >
> > > I run samba sharing NFS mounted shares from another machine. I'm getting
> > > the following bugs in console (and in logs), when I stop samba (but not
> > > always, I think it depends of stalled locks):
> > >
> > > lockd: unexpected unlock status: 7
> > > lockd: unexpected unlock status: 7
> > > lockd: unexpected unlock status: 7
> > > ------------[ cut here ]------------
> >
> > Hmm... The problem here is that the server is returning an unexpected
> > error: it is normally supposed to return "lock granted" or "grace
> > error", but is actually returning "stale filehandle".
> >
> > Anyhow, the client should be able to deal with this without Oopsing.
>
>
> This seems to be a patch that should go into 2.6.16?
>
I'd agree and suggest that it also be send to -stable since it fixes a
crash actually seen "in the wild".
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-02-25 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 15:15 Fermin Molina
2006-02-19 18:27 ` Trond Myklebust
2006-02-25 15:35 ` Adrian Bunk
2006-02-25 15:46 ` Jesper Juhl [this message]
2006-02-25 16:04 ` Trond Myklebust
2006-02-27 22:56 ` Fermin Molina
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=9a8748490602250746m30745f30sfe989ff4b2a1ecf2@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=bunk@stusta.de \
--cc=fermin@asic.udl.es \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®