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] 2.6.8.1 deadlock in rpc_queue_lock <<===>> rpc_sched_lock
Date: Wed, 08 Sep 2004 13:51:00 +1000 [thread overview]
Message-ID: <1094615460.20243.165.camel@hole.melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409071915020.23546@coverity.dreamhost.com>
On Wed, 2004-09-08 at 12:15, Dawson Engler wrote:
> Hi All,
>
> below is a possible deadlock in linux-2.6.8.1 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 error is in debugging code so maybe
> not such a big deal).
>
>[...]
> /u2/engler/mc/oses/linux/linux-2.6.8.1/net/sunrpc/sched.c:__rpc_wake_up_task
> 430: __rpc_wake_up_task(struct rpc_task *task)
> 431: {
> 432: dprintk("RPC: %4d __rpc_wake_up_task (now %ld inh %d)\n",
> 433: task->tk_pid, jiffies, rpc_inhibit);
> 434:
> 435: #ifdef RPC_DEBUG
> 436: if (task->tk_magic != 0xf00baa) {
> 437: printk(KERN_ERR "RPC: attempt to wake up non-existing task!\n");
> 438: rpc_debug = ~0;
> ===> 439: rpc_show_tasks();
If this arc ever happens, you have data structure corruption issues
which are far more worrying than a deadlock.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
next prev parent reply other threads:[~2004-09-08 3:44 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 [this message]
2004-09-08 4:23 ` Trond Myklebust
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=1094615460.20243.165.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®