From: malahal@us.ibm.com
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Matthew Wilcox <matthew@wil.cx>, linux-scsi@vger.kernel.org
Subject: Re: blk request timeout handler against 2.6.26
Date: Mon, 12 May 2008 20:20:12 -0700 [thread overview]
Message-ID: <20080513032012.GC9511@us.ibm.com> (raw)
In-Reply-To: <20080507074357.GP329@kernel.dk>
Add missing queue lock in blk_complete_request(). Ran disktest for few
hours and it works fine with this patch.
Signed-off-by: Malahal Naineni <malahal@us.ibm.com>
diff -r c06b3eb1f516 block/blk-core.c
--- a/block/blk-core.c Wed May 07 20:07:12 2008 -0700
+++ b/block/blk-core.c Wed May 07 20:17:03 2008 -0700
@@ -1856,6 +1856,10 @@
*/
void blk_complete_request(struct request *req)
{
+ unsigned long flags;
+ struct request_queue *q = req->q;
+ int rc;
+
/*
* We don't have to worry about this one timing out any more.
* If we are unable to remove the timer, then the command
@@ -1864,7 +1868,10 @@
* that function could really be. It might be on another processor,
* etc, etc.
*/
- if (!blk_delete_timer(req))
+ spin_lock_irqsave(q->queue_lock, flags);
+ rc = blk_delete_timer(req);
+ spin_unlock_irqrestore(q->queue_lock, flags);
+ if (!rc)
return;
__blk_complete_request(req);
next prev parent reply other threads:[~2008-05-13 3:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 2:00 blk request timeout handler against 2.6.26 Matthew Wilcox
2008-05-03 13:20 ` Matthew Wilcox
2008-05-06 1:47 ` malahal
2008-05-07 7:43 ` Jens Axboe
2008-05-13 3:16 ` malahal
2008-05-13 3:19 ` blk request timeout minor fixes malahal
2008-05-13 3:20 ` malahal [this message]
2008-06-19 17:17 ` blk request timeout handler against 2.6.26 Mike Anderson
2008-06-20 8:37 ` Jens Axboe
2008-06-24 10:16 ` Jens Axboe
2008-07-02 19:43 ` malahal
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=20080513032012.GC9511@us.ibm.com \
--to=malahal@us.ibm.com \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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.