mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Saout <christophe@saout.de>
To: linux-kernel@vger.kernel.org
Cc: NFS V4 Mailing List <nfsv4@linux-nfs.org>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	"J. Bruce Fields" <bfields@citi.umich.edu>,
	Olaf Kirch <okir@monad.swb.de>
Subject: [PATCH] Fix SUNRPC wakeup/execute race condition
Date: Sun, 05 Nov 2006 02:04:48 +0100	[thread overview]
Message-ID: <1162688688.5153.26.camel@leto.intern.saout.de> (raw)
In-Reply-To: <1162602386.26794.5.camel@leto.intern.saout.de>

The sunrpc scheduler contains a race condition that can let an RPC
task end up being neither running nor on any wait queue. The race takes
place between rpc_make_runnable (called from rpc_wake_up_task) and
__rpc_execute under the following condition:

First __rpc_execute calls tk_action which puts the task on some wait
queue. The task is dequeued by another process before __rpc_execute
continues its execution. While executing rpc_make_runnable exactly after
setting the task `running' bit and before clearing the `queued' bit
__rpc_execute picks up execution, clears `running' and subsequently
both functions fall through, both under the false assumption somebody
else took the job.

Swapping rpc_test_and_set_running with rpc_clear_queued in
rpc_make_runnable fixes that hole. The reordering hopefully doesn't
introduce some new race condition, in fact the only possible one is
already correctly detected and handled in __rpc_execute.

Bug noticed on a 4-way x86_64 system under XEN with an NFSv4 server
on the same physical machine, apparently one of the few ways to hit
this race condition at all.

Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: J. Bruce Fields <bfields@citi.umich.edu>
Cc: Olaf Kirch <okir@monad.swb.de>
Signed-off-by: Christophe Saout <christophe@saout.de>

--- linux-2.6.18/net/sunrpc/sched.c	2006-09-20 05:42:06.000000000 +0200
+++ linux/net/sunrpc/sched.c	2006-11-04 20:38:56.000000000 +0100
@@ -302,12 +302,9 @@ EXPORT_SYMBOL(__rpc_wait_for_completion_
  */
 static void rpc_make_runnable(struct rpc_task *task)
 {
-	int do_ret;
-
 	BUG_ON(task->tk_timeout_fn);
-	do_ret = rpc_test_and_set_running(task);
 	rpc_clear_queued(task);
-	if (do_ret)
+	if (rpc_test_and_set_running(task))
 		return;
 	if (RPC_IS_ASYNC(task)) {
 		int status;



       reply	other threads:[~2006-11-05  1:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1157576316.3292.13.camel@dyn9047022153>
     [not found] ` <20060907150146.GA22586@fieldses.org>
     [not found]   ` <1157731084.3292.25.camel@dyn9047022153>
     [not found]     ` <20060908160432.GB19234@fieldses.org>
     [not found]       ` <1162158228.11247.4.camel@leto.intern.saout.de>
     [not found]         ` <1162159282.11247.17.camel@leto.intern.saout.de>
     [not found]           ` <1162321027.23543.6.camel@leto.intern.saout.de>
     [not found]             ` <1162324141.23543.23.camel@leto.intern.saout.de>
     [not found]               ` <1162325490.5614.82.camel@lade.trondhjem.org>
     [not found]                 ` <1162602386.26794.5.camel@leto.intern.saout.de>
2006-11-05  1:04                   ` Christophe Saout [this message]
2006-11-05  6:50                     ` Trond Myklebust
2006-11-05 10:32                       ` Christophe Saout
2006-11-05 17:01                         ` Trond Myklebust
2006-11-05 17:42                           ` Christophe Saout
2006-11-08 18:34                             ` 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=1162688688.5153.26.camel@leto.intern.saout.de \
    --to=christophe@saout.de \
    --cc=bfields@citi.umich.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfsv4@linux-nfs.org \
    --cc=okir@monad.swb.de \
    --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 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®