From: Greg Banks <gnb@melbourne.sgi.com>
To: Dawson Engler <engler@coverity.dreamhost.com>
Cc: linux-kernel@vger.kernel.org, developers@coverity.com
Subject: Re: [CHECKER] potential NFS deadlock in 2.6.8.1
Date: Wed, 08 Sep 2004 13:29:34 +1000 [thread overview]
Message-ID: <1094614173.20243.159.camel@hole.melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409071949070.28006@coverity.dreamhost.com>
On Wed, 2004-09-08 at 12:49, Dawson Engler wrote:
> Hi All,
>
> below is a possible deadlock in the linux-2.6.8.1 NFS found by a static
> deadlock checker I'm writing. Let me know if it looks valid and/or
> whether the output is too cryptic.
Your static analysis and presentation is fine (nice work). However
the deadlock can't occur in practice because the nfs4_state_shutdown()
function is only called from nfsd() by the last nfsd thread to die
when NFS is being shut down, so there is no thread B to deadlock with.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
prev parent reply other threads:[~2004-09-08 3:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 2:49 Dawson Engler
2004-09-08 3:08 ` Nick Piggin
2004-09-08 3:29 ` Greg Banks [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=1094614173.20243.159.camel@hole.melbourne.sgi.com \
--to=gnb@melbourne.sgi.com \
--cc=developers@coverity.com \
--cc=engler@coverity.dreamhost.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®