From: Jens Axboe <axboe@suse.de>
To: Nick Piggin <piggin@cyberone.com.au>,
Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@osdl.org>
Subject: AS spin lock bugs
Date: Thu, 13 Nov 2003 11:38:23 +0100 [thread overview]
Message-ID: <20031113103823.GB4441@suse.de> (raw)
Hi,
Was looking at io tracking for cfq, and I think I found some spin lock
bugs in current as (current BK). as_update_iohist() runs from
add_request which is typically in process context. It could be run with
interrupts disabled though, either driver private stuff or using the
generic block layer tagging.
Anyways, as_update_iohist() grabs aic->lock without disabling
interrupts, while as_completed_request() typically runs at interrupt
time and grabs the same lock. Deadlock.
To be safe, both need to use the flags saving lock variants.
===== drivers/block/as-iosched.c 1.28 vs edited =====
--- 1.28/drivers/block/as-iosched.c Mon Nov 10 06:12:07 2003
+++ edited/drivers/block/as-iosched.c Thu Nov 13 11:37:47 2003
@@ -783,14 +783,14 @@
{
struct as_rq *arq = RQ_DATA(rq);
int data_dir = arq->is_sync;
- unsigned long thinktime;
+ unsigned long thinktime, flags;
sector_t seek_dist;
if (aic == NULL)
return;
if (data_dir == REQ_SYNC) {
- spin_lock(&aic->lock);
+ spin_lock_irqsave(&aic->lock, flags);
if (test_bit(AS_TASK_IORUNNING, &aic->state)
&& !atomic_read(&aic->nr_queued)
@@ -844,7 +844,7 @@
aic->seek_total = (aic->seek_total>>1)
+ (aic->seek_total>>2);
- spin_unlock(&aic->lock);
+ spin_unlock_irqrestore(&aic->lock, flags);
}
}
@@ -909,6 +909,7 @@
struct as_data *ad = q->elevator.elevator_data;
struct as_rq *arq = RQ_DATA(rq);
struct as_io_context *aic;
+ unsigned long flags;
WARN_ON(!list_empty(&rq->queuelist));
@@ -959,12 +960,12 @@
if (!aic)
return;
- spin_lock(&aic->lock);
+ spin_lock_irqsave(&aic->lock, flags);
if (arq->is_sync == REQ_SYNC) {
set_bit(AS_TASK_IORUNNING, &aic->state);
aic->last_end_request = jiffies;
}
- spin_unlock(&aic->lock);
+ spin_unlock_irqrestore(&aic->lock, flags);
put_io_context(arq->io_context);
}
--
Jens Axboe
next reply other threads:[~2003-11-13 10:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 10:38 Jens Axboe [this message]
2003-11-13 10:52 ` AS spin lock bugs Nick Piggin
2003-11-13 10:59 ` Jens Axboe
2003-11-13 10:52 ` Jens Axboe
2003-11-13 10:59 ` Nick Piggin
2003-11-13 11:01 ` Jens Axboe
2003-11-13 11:10 ` Jens Axboe
2003-11-13 11:16 ` Nick Piggin
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=20031113103823.GB4441@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=torvalds@osdl.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