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] possible deadlock in 2.6.8.1 lockd code
Date: Wed, 08 Sep 2004 13:45:46 +1000 [thread overview]
Message-ID: <1094615146.20243.162.camel@hole.melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409071956380.6778@coverity.dreamhost.com>
On Wed, 2004-09-08 at 12:57, Dawson Engler wrote:
> Hi All,
>
> below is a possible deadlock in the linux-2.6.8.1 lockd code found by a
> static deadlock checker I'm writing. Let me know if it looks valid and/or
> whether the output is too cryptic. (Note, the locking dependencies go
> across a bunch of function calls, so the paths may be infeasible.)
Nick's comment applies here. Furthermore, there is at most one lockd
thread so once again 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:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 2:57 Dawson Engler
2004-09-08 3:28 ` Trond Myklebust
2004-09-08 3:34 ` viro
2004-09-08 3:45 ` 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=1094615146.20243.162.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®