From: Jonathan Couper <jonathan-3c88B9b11vOEi8DpZVb4nw@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: Mutex Hang on GC in lockd for 2.6.22-14
Date: Mon, 21 Jan 2008 18:24:52 +1300 [thread overview]
Message-ID: <47942CA4.1060700@spiderfan.org> (raw)
In-Reply-To: <18324.11227.8442.938224-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
Heya NFS Experts,
I'm pretty darn sure I've found (and am currently testing a fix for) a
mutex bug in lockd that hangs NFS server pretty reliably. I have no
idea how this bug has gone unnoticed for so long, since this is the
current Gutsy Gibbon kernel!
That makes me think that maybe I'm mistaken. But my system definitely
hangs, and the code definitely appears to attempt to lock twice on a
non-recursive mutex.
All the details are:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/181996
I'd LOVE to get my name into the Linux Kernel. Please tell me I've
found a real bug!
J.
Neil Brown wrote:
> On Monday January 21, jonathan-3c88B9b11vOEi8DpZVb4nw@public.gmane.org wrote:
>> Heya,
>>
>> I'm pretty darn sure I've found (and am currently testing a fix for) a
>> mutex bug in lockd that hangs NFS server pretty reliably. I have no
>> idea how this bug has gone unnoticed for so long, since this is the
>> current Gutsy Gibbon kernel!
>>
>> That makes me think that maybe I'm mistaken. But my system definitely
>> hangs, and the code definitely appears to attempt to lock twice on a
>> non-recursive mutex.
>>
>> All the details are:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/181996
>>
>> I'd LOVE to get my name into the Linux Kernel. Please tell me I've
>> found a real bug!
>>
>> J.
>
> I'll probably have a look, but please post this to
> linux-nfs@vger.kernel.org
>
> other people have interest in, and knowledge of, lockd. Not just me.
>
> Thanks,
> NeilBrown
>
next parent reply other threads:[~2008-01-21 5:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <479427C5.8020203@spiderfan.org>
[not found] ` <18324.11227.8442.938224@notabene.brown>
[not found] ` <18324.11227.8442.938224-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-01-21 5:24 ` Jonathan Couper [this message]
[not found] ` <47942CA4.1060700-3c88B9b11vOEi8DpZVb4nw@public.gmane.org>
2008-01-21 18:31 ` Mutex Hang on GC in lockd for 2.6.22-14 J. Bruce Fields
2008-01-21 20:49 ` Jonathan Couper
[not found] ` <47950544.2080205-3c88B9b11vOEi8DpZVb4nw@public.gmane.org>
2008-01-21 21:03 ` J. Bruce Fields
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=47942CA4.1060700@spiderfan.org \
--to=jonathan-3c88b9b11voei8dpzvb4nw@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox