s390/dasd: Store path configuration data during path handling
authorJan Höppner <hoeppner@linux.ibm.com>
Thu, 8 Oct 2020 13:13:32 +0000 (15:13 +0200)
committerJens Axboe <axboe@kernel.dk>
Mon, 16 Nov 2020 15:14:38 +0000 (08:14 -0700)
commit460181217a2496defc6c279b0a7eb810b05b9145
tree93471bca91b533034347070c56218350abe1fb47
parentd2a527580c0a0c83f1d98eff32804cde4280d721
s390/dasd: Store path configuration data during path handling

Currently, the configuration data for a path is retrieved during a path
verification and used only temporarily. If a path is newly added to the
I/O setup after a boot, no configuration data will be stored for this
particular path.
However, this data is required for later use and should be present for
a valid I/O path anyway. Store this data during the path verification so
that newly added paths can provide all information necessary.

[sth@linux.ibm.com: fix conf_data memleak]

Signed-off-by: Jan Höppner <hoeppner@linux.ibm.com>
Signed-off-by: Stefan Haberland <sth@linux.ibm.com>
Reviewed-by: Stefan Haberland <sth@linux.ibm.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
drivers/s390/block/dasd_eckd.c