[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <200610111119.k9BBJhls004763@vass.7ka.mipt.ru>
Date: Wed, 11 Oct 2006 15:19:43 +0400
From: Vasily Tarasov <vtaras@...nvz.org>
To: Jens Axboe <axboe@...e.de>
CC: OpenVZ Developer List <devel@...nvz.org>
Subject: [PATCH] block layer: elv_iosched_show should get elv_list_lock
elv_iosched_show function iterates other elv_list,
hence elv_list_lock should be got.
Also the question is: in elv_iosched_show, elv_iosched_store
q->elevator->elevator_type construction is used without locking q->queue_lock.
Is it expected?..
Signed-off-by: Vasily Tarasov <vtaras@...nvz.org>
--
--- linux-2.6.18/block/elevator.c.orig 2006-10-11 11:00:34.000000000 +0400
+++ linux-2.6.18/block/elevator.c 2006-10-11 15:08:20.000000000 +0400
@@ -892,7 +892,7 @@ ssize_t elv_iosched_show(request_queue_t
struct list_head *entry;
int len = 0;
- spin_lock_irq(q->queue_lock);
+ spin_lock_irq(&elv_list_lock);
list_for_each(entry, &elv_list) {
struct elevator_type *__e;
@@ -902,7 +902,7 @@ ssize_t elv_iosched_show(request_queue_t
else
len += sprintf(name+len, "%s ", __e->elevator_name);
}
- spin_unlock_irq(q->queue_lock);
+ spin_unlock_irq(&elv_list_lock);
len += sprintf(len+name, "\n");
return len;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists