a94204e132
side-effect of registering them, config_detach(9) cleared DVF_ACTIVE before it called wddetach() or sddetach(). Even though sd(4)'s detachment may have subsequently failed with EBUSY, we could not begin new disk I/O on sd(4) because the device had been deactivated. By analogy to sdstrategy(), test device_is_active() in wdstrategy() and if it is false set b_errno to EIO instead of initiating new disk I/O. XXX We should decline more politely to start new I/O, since XXX !device_is_active() may mean simply that the device is suspended. XXX I suppose that EIO is safe as long as system suspension is XXX all-or-nothing. |
||
---|---|---|
.. | ||
ata_raid_adaptec.c | ||
ata_raid_intel.c | ||
ata_raid_jmicron.c | ||
ata_raid_nvidia.c | ||
ata_raid_promise.c | ||
ata_raid_subr.c | ||
ata_raid_via.c | ||
ata_raid.c | ||
ata_raidreg.h | ||
ata_raidvar.h | ||
ata_wdc.c | ||
ata.c | ||
ataconf.h | ||
atareg.h | ||
atavar.h | ||
files.ata | ||
ld_ataraid.c | ||
Makefile | ||
sata_subr.c | ||
satapmpreg.h | ||
satareg.h | ||
satavar.h | ||
wd.c | ||
wdvar.h |