diff options
| author | Stefan Haberland | 2023-07-21 21:36:44 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman | 2023-08-03 10:24:16 +0200 |
| commit | c4ae208cc335afad6b219edc03a07f022a897514 (patch) | |
| tree | 106a8feb061120e3512d6c980e258450656c91e7 /mm/page_poison.c | |
| parent | 2b58bd384730ac2cd177fd8e4d0bf0aa4a0bf166 (diff) | |
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: 8e09f21574ea ("[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>
Diffstat (limited to 'mm/page_poison.c')
0 files changed, 0 insertions, 0 deletions