[S390] dasd: fix panic caused by alias device offline
When an alias device is set offline while it is in use this may result in a panic in the cleanup part of the dasd_block_tasklet. The problem here is that there may exist some ccw requests that were originally created for the alias device and transferred to the base device when the alias was set offline. When these request are cleaned up later, the discipline pointer in the alias device may not be valid anymore. To fix this use the base device discipline to find the cleanup function. Signed-off-by: Stefan Weinhuber <wein@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
This commit is contained in:
parent
6c5f57c788
commit
fe6b8e76d9
@ -1706,7 +1706,7 @@ static void __dasd_cleanup_cqr(struct dasd_ccw_req *cqr)
|
|||||||
|
|
||||||
req = (struct request *) cqr->callback_data;
|
req = (struct request *) cqr->callback_data;
|
||||||
dasd_profile_end(cqr->block, cqr, req);
|
dasd_profile_end(cqr->block, cqr, req);
|
||||||
status = cqr->memdev->discipline->free_cp(cqr, req);
|
status = cqr->block->base->discipline->free_cp(cqr, req);
|
||||||
if (status <= 0)
|
if (status <= 0)
|
||||||
error = status ? status : -EIO;
|
error = status ? status : -EIO;
|
||||||
dasd_end_request(req, error);
|
dasd_end_request(req, error);
|
||||||
|
Loading…
Reference in New Issue
Block a user