From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: Dawson Engler <engler@coverity.dreamhost.com>,
linux-kernel@vger.kernel.org, developers@coverity.com
Subject: Re: [CHECKER] 2.6.8.1 deadlock in rpc_queue_lock <<===>> rpc_sched_lock
Date: Wed, 08 Sep 2004 00:23:48 -0400 [thread overview]
Message-ID: <1094617428.8389.12.camel@lade.trondhjem.org> (raw)
In-Reply-To: <1094615460.20243.165.camel@hole.melbourne.sgi.com>
På ty , 07/09/2004 klokka 23:51, skreiv Greg Banks:
> If this arc ever happens, you have data structure corruption issues
> which are far more worrying than a deadlock.
True, but we should still get rid of it. No point in maintaining buggy
debugging lines.
Note that in any case, the global rpc_queue_lock is gone in recent
NFS_ALL and 2.6.x-mm series patches.
Cheers,
Trond
prev parent reply other threads:[~2004-09-08 4:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 2:15 Dawson Engler
2004-09-08 3:51 ` Greg Banks
2004-09-08 4:23 ` Trond Myklebust [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=1094617428.8389.12.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=developers@coverity.com \
--cc=engler@coverity.dreamhost.com \
--cc=gnb@melbourne.sgi.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®