Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Stefan Haberland 00748bc586 s390/dasd: fix hanging device after quiesce/resume ... commit 05f1d8ed03f547054efbc4d29bb7991c958ede95 upstream. Quiesce and resume are functions that tell the DASD driver to stop/resume issuing I/Os to a specific DASD. On resume dasd_schedule_block_bh() is called to kick handling of IO requests again. This does unfortunately not cover internal requests which are used for path verification for example. This could lead to a hanging device when a path event or anything else that triggers internal requests occurs on a quiesced device. Fix by also calling dasd_schedule_device_bh() which triggers handling of internal requests on resume. Fixes: 8e09f21574 ("[S390] dasd: add hyper PAV support to DASD device driver, part 1") Cc: stable@vger.kernel.org Signed-off-by: Stefan Haberland <sth@linux.ibm.com> Reviewed-by: Jan Hoeppner <hoeppner@linux.ibm.com> Link: https://lore.kernel.org/r/20230721193647.3889634-2-sth@linux.ibm.com Signed-off-by: Jens Axboe <axboe@kernel.dk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2023-08-11 11:53:53 +02:00
..
block	s390/dasd: fix hanging device after quiesce/resume	2023-08-11 11:53:53 +02:00
char
cio	s390/cio: unregister device when the only path is gone	2023-06-28 10:18:41 +02:00
crypto
net
scsi
virtio
Makefile