diff options
| author | Amit Shah <amit.shah@redhat.com> | 2013-07-29 14:23:21 +0930 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-08-14 22:55:17 -0700 |
| commit | 1336e0d81c7ea5128f87993907aaff3db71bf973 (patch) | |
| tree | dc7db7247bdc4a32ec64db977f7a40201552e129 /fs | |
| parent | 7ba6337874c92f15212065b120fa70de573c56ed (diff) | |
| download | kernel_samsung_smdk4412-1336e0d81c7ea5128f87993907aaff3db71bf973.zip kernel_samsung_smdk4412-1336e0d81c7ea5128f87993907aaff3db71bf973.tar.gz kernel_samsung_smdk4412-1336e0d81c7ea5128f87993907aaff3db71bf973.tar.bz2 | |
virtio: console: return -ENODEV on all read operations after unplug
commit 96f97a83910cdb9d89d127c5ee523f8fc040a804 upstream.
If a port gets unplugged while a user is blocked on read(), -ENODEV is
returned. However, subsequent read()s returned 0, indicating there's no
host-side connection (but not indicating the device went away).
This also happened when a port was unplugged and the user didn't have
any blocking operation pending. If the user didn't monitor the SIGIO
signal, they won't have a chance to find out if the port went away.
Fix by returning -ENODEV on all read()s after the port gets unplugged.
write() already behaves this way.
Signed-off-by: Amit Shah <amit.shah@redhat.com>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions