s390/dasd: fix invalid PAV assignment after suspend/resume
authorStefan Haberland <stefan.haberland@de.ibm.com>
Thu, 15 Oct 2015 11:54:39 +0000 (13:54 +0200)
committerMartin Schwidefsky <schwidefsky@de.ibm.com>
Tue, 3 Nov 2015 13:40:46 +0000 (14:40 +0100)
commit251afd69e3328653bae4a8ca09700971ca4000c5
treec1a3ba142c40d225d238e2ae28ada7b146e230e9
parentc7c0c9deb0a4b0715d2c09438420437b86f387c4
s390/dasd: fix invalid PAV assignment after suspend/resume

For a valid PAV assignment the DASD driver needs to notice possibly
changed configuration data. Thus the failing of read configuration
data should also fail the device restore to prevent invalid PAV
assignment. The failed device may get restored after additional paths
get available later on.
If the restore fails after the device was added to the lcu alias
handling it needs to be removed from the alias handling before exiting
the restore function.

Reviewed-by: Sebastian Ott <sebott@linux.vnet.ibm.com>
Signed-off-by: Stefan Haberland <stefan.haberland@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
drivers/s390/block/dasd_eckd.c