From: Stephen M. Cameron Date: Thu, 17 Sep 2009 18:48:05 +0000 (-0500) Subject: cciss: Don't check h->busy_initializing in cciss_open(). X-Git-Tag: 2.1b_release~10246^2~114 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=2e043986d584cf95656d4ee0c40fb2051e8a8460;p=platform%2Fkernel%2Fkernel-mfld-blackbay.git cciss: Don't check h->busy_initializing in cciss_open(). Don't check h->busy_initializing in cciss_open(). Open won't be called before things are ready, but h->busy_initializing won't be unset until after the initial rebuild_lun_table is finished. But, to read the partitions, cciss_open will be called for each logical drive during rebuild_lun_table. If cciss_open checks h->busy_initializing, then the reading of the partition information during the initial rebuild_lun_table will fail, which is especially bad news if it happens to be your boot device. Signed-off-by: Stephen M. Cameron Signed-off-by: Jens Axboe --- diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c index d6ea937..79afca2 100644 --- a/drivers/block/cciss.c +++ b/drivers/block/cciss.c @@ -830,7 +830,7 @@ static int cciss_open(struct block_device *bdev, fmode_t mode) printk(KERN_DEBUG "cciss_open %s\n", bdev->bd_disk->disk_name); #endif /* CCISS_DEBUG */ - if (host->busy_initializing || drv->busy_configuring) + if (drv->busy_configuring) return -EBUSY; /* * Root is allowed to open raw volume zero even if it's not configured