diff options
author | Greg Kurz <groug@kaod.org> | 2017-01-13 18:18:20 +0100 |
---|---|---|
committer | Greg Kurz <groug@kaod.org> | 2017-01-25 09:34:35 +0100 |
commit | 0d78289c3dca3de8e614a551a3d4a9415168ace0 (patch) | |
tree | 9953e626189e053bcbd95ecba74917b91b587a88 /hw/9pfs/9p-local.c | |
parent | 6e37f458d2381d3572f94fa0ce5487a3e17209fa (diff) | |
download | qemu-0d78289c3dca3de8e614a551a3d4a9415168ace0.zip qemu-0d78289c3dca3de8e614a551a3d4a9415168ace0.tar.gz qemu-0d78289c3dca3de8e614a551a3d4a9415168ace0.tar.bz2 |
9pfs: fix off-by-one error in PDU free list
The server can handle MAX_REQ - 1 PDUs at a time and the virtio-9p
device has a MAX_REQ sized virtqueue. If the client manages to fill
up the virtqueue, pdu_alloc() will fail and the request won't be
processed without any notice to the client (it actually causes the
linux 9p client to hang).
This has been there since the beginning (commit 9f10751365b2 "virtio-9p:
Add a virtio 9p device to qemu"), but it needs an agressive workload to
run in the guest to show up.
We actually allocate MAX_REQ PDUs and I see no reason not to link them
all into the free list, so let's fix the init loop.
Reported-by: Tuomas Tynkkynen <tuomas@tuxera.com>
Suggested-by: Al Viro <viro@ZenIV.linux.org.uk>
Signed-off-by: Greg Kurz <groug@kaod.org>
Diffstat (limited to 'hw/9pfs/9p-local.c')
0 files changed, 0 insertions, 0 deletions