diff options
| author | Stefan Haberland <sth@linux.vnet.ibm.com> | 2016-09-20 10:42:38 +0200 |
|---|---|---|
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2016-09-26 16:45:29 +0200 |
| commit | c020d722b110a44c613ef71e657e6dd4116e09d9 (patch) | |
| tree | 5fc0f6d62335cb7075f6a162380ee54c1b3ea069 /arch/alpha | |
| parent | a9f6273ff9c80dd2c226f7a2d5c16272e5092d3e (diff) | |
| download | linux-stable-c020d722b110a44c613ef71e657e6dd4116e09d9.tar.gz linux-stable-c020d722b110a44c613ef71e657e6dd4116e09d9.tar.bz2 linux-stable-c020d722b110a44c613ef71e657e6dd4116e09d9.zip | |
s390/dasd: fix panic during offline processing
A DASD device consists of the device itself and a discipline with a
corresponding private structure. These fields are set up during online
processing right after the device is created and before it is processed by
the state machine and made available for I/O.
During offline processing the discipline pointer and the private data gets
freed within the state machine and without protection of the existing
reference count. This might lead to a kernel panic because a function might
have taken a device reference and accesses the discipline pointer and/or
private data of the device while this is already freed.
Fix by freeing the discipline pointer and the private data after ensuring
that there is no reference to the device left.
Reviewed-by: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
Signed-off-by: Stefan Haberland <sth@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'arch/alpha')
0 files changed, 0 insertions, 0 deletions