From: Olaf Kirch <okir@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] prevent sunrpc deadlock with debug on
Date: Wed, 5 Jan 2005 17:44:55 +0100 [thread overview]
Message-ID: <20050105164455.GI26856@suse.de> (raw)
In-Reply-To: <1104277396.3976.10.camel@lade.trondhjem.org>
Hi Trond,
On Wed, Dec 29, 2004 at 12:43:16AM +0100, Trond Myklebust wrote:
> I think I've found the real bug that Shirly was seeing. Can you ask her
> to test if this change fixes the actual problem?
I don't think that will be possible, but I'll ask her. The patch does
look correct though.
Still, if we ever run into a corrupted task struct, we will still
deadlock. How about this:
show_tasks(void)
{
struct list_head *le;
struct rpc_task *t;
- spin_lock(&rpc_sched_lock);
+ if (!spin_trylock(&rpc_sched_lock))
+ return;
if (list_empty(&all_tasks)) {
spin_unlock(&rpc_sched_lock);
Olaf
--
Olaf Kirch | Things that make Monday morning interesting, #2:
okir@suse.de | "We have 8,000 NFS mount points, why do we keep
---------------+ running out of privileged ports?"
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-01-05 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 16:57 [PATCH] prevent sunrpc deadlock with debug on Olaf Kirch
2004-12-28 23:43 ` Trond Myklebust
2005-01-05 16:44 ` Olaf Kirch [this message]
2005-01-05 17:21 ` 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=20050105164455.GI26856@suse.de \
--to=okir@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.