summaryrefslogtreecommitdiffstats
path: root/lib/bug.c
diff options
context:
space:
mode:
authorStefan Haberland <sth@linux.ibm.com>2019-08-01 13:06:30 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-08-06 19:08:18 +0200
commit79977e8995541d7a0671305d0df053e3bc54366a (patch)
tree05967c32b60275dfd5e607e79098816aaf0d1bdd /lib/bug.c
parent4c825540af16197d84e6cf943972eccf6ea54ff6 (diff)
downloadlinux-stable-79977e8995541d7a0671305d0df053e3bc54366a.tar.gz
linux-stable-79977e8995541d7a0671305d0df053e3bc54366a.tar.bz2
linux-stable-79977e8995541d7a0671305d0df053e3bc54366a.zip
s390/dasd: fix endless loop after read unit address configuration
commit 41995342b40c418a47603e1321256d2c4a2ed0fb upstream. After getting a storage server event that causes the DASD device driver to update its unit address configuration during a device shutdown there is the possibility of an endless loop in the device driver. In the system log there will be ongoing DASD error messages with RC: -19. The reason is that the loop starting the ruac request only terminates when the retry counter is decreased to 0. But in the sleep_on function there are early exit paths that do not decrease the retry counter. Prevent an endless loop by handling those cases separately. Remove the unnecessary do..while loop since the sleep_on function takes care of retries by itself. Fixes: 8e09f21574ea ("[S390] dasd: add hyper PAV support to DASD device driver, part 1") Cc: stable@vger.kernel.org # 2.6.25+ Signed-off-by: Stefan Haberland <sth@linux.ibm.com> Reviewed-by: Jan Hoeppner <hoeppner@linux.ibm.com> Signed-off-by: Jens Axboe <axboe@kernel.dk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'lib/bug.c')
0 files changed, 0 insertions, 0 deletions