| commit | 2e043986d584cf95656d4ee0c40fb2051e8a8460 | |
| author | Stephen M. Cameron <scameron@beardog.cce.hp.com> | |
| Thu, 17 Sep 2009 18:48:05 +0000 (17 13:48 -0500) | ||
| committer | Jens Axboe <jens.axboe@oracle.com> | |
| Thu, 1 Oct 2009 19:15:43 +0000 (1 21:15 +0200) | ||
| tree | 9a1cfc5fb0fd8ec639bd239e464f59298e588106 | treesnapshot (tar.gz zip) |
| parent | 39ccf9a645dbca7f9866317380912327570787c0 | commitdiff |
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 <scameron@beardog.cce.hp.com>
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
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 <scameron@beardog.cce.hp.com>
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
| drivers/block/cciss.c | diffblobblamehistory |