diff options
| author | Sebastian Ott <sebott@linux.vnet.ibm.com> | 2018-02-06 14:59:43 +0100 |
|---|---|---|
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2018-02-22 10:09:22 +0100 |
| commit | f97a6b6c47d2f329a24f92cc0ca3c6df5727ba73 (patch) | |
| tree | 3529b1e31395d451cc5c6a6bcd58adb42c0fe9dd /net/rfkill | |
| parent | dc24b7b49a53c7ee5502c877b133558acec0b3f8 (diff) | |
| download | linux-stable-f97a6b6c47d2f329a24f92cc0ca3c6df5727ba73.tar.gz linux-stable-f97a6b6c47d2f329a24f92cc0ca3c6df5727ba73.tar.bz2 linux-stable-f97a6b6c47d2f329a24f92cc0ca3c6df5727ba73.zip | |
s390/cio: fix ccw_device_start_timeout API
There are cases a device driver can't start IO because the device is
currently in use by cio. In this case the device driver is notified
when the device is usable again.
Using ccw_device_start_timeout we would set the timeout (and change
an existing timeout) before we test for internal usage. Worst case
this could lead to an unexpected timer deletion.
Fix this by setting the timeout after we test for internal usage.
Signed-off-by: Sebastian Ott <sebott@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'net/rfkill')
0 files changed, 0 insertions, 0 deletions