From: Olaf Kirch <okir@suse.de>
To: Jan Sanislo <oystr@cs.washington.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: Bug in nfs client handling of EJUKEBOX
Date: Thu, 24 Feb 2005 12:55:31 +0100 [thread overview]
Message-ID: <20050224115531.GF11336@suse.de> (raw)
In-Reply-To: <1109101592/oystr@hugh.cs.washington.edu>
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
> If the tk_exit procedure (e.g., nfs_read_done) called at ">>>>" above
> detects EJUKEBOX as the result of the call, it will attempt to do
> an rpc_restart and rpc_delay on the task. The rpc_delay will set a timer.
> However, when the main loop is re-entered via the "goto restarted",
> the first thing that happens is that all timers for the task are removed.
> This results in the RPC task hanging in an uninterruptible wait.
>
> Am I missing something here or is this really a problem?
I think this is a genuine problem. Previously, we would clear the timers
only when the task was running, i.e. inside the if (RPC_RUNNING(task))
branch. Proposed patch attached.
Olaf
--
Olaf Kirch | --- o --- Nous sommes du soleil we love when we play
okir@suse.de | / | \ sol.dhoop.naytheet.ah kin.ir.samse.qurax
[-- Attachment #2: sunrpc-restart-delay-fix --]
[-- Type: text/plain, Size: 432 bytes --]
Index: linux-2.6.10/net/sunrpc/sched.c
===================================================================
--- linux-2.6.10.orig/net/sunrpc/sched.c
+++ linux-2.6.10/net/sunrpc/sched.c
@@ -569,7 +569,8 @@ static int __rpc_execute(struct rpc_task
/*
* Garbage collection of pending timers...
*/
- rpc_delete_timer(task);
+ if (RPC_IS_RUNNING(task))
+ rpc_delete_timer(task);
/*
* Execute any pending callback.
next prev parent reply other threads:[~2005-02-24 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 19:46 Bug in nfs client handling of EJUKEBOX Jan Sanislo
2005-02-24 11:55 ` Olaf Kirch [this message]
2005-02-24 20:02 ` Trond Myklebust
2005-02-25 9:29 ` Olaf Kirch
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=20050224115531.GF11336@suse.de \
--to=okir@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=oystr@cs.washington.edu \
/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.