diff options
| author | Kevin Wolf <kwolf@redhat.com> | 2021-07-27 17:49:23 +0200 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2021-08-03 15:43:30 +0200 |
| commit | 87ab88025247b893aad5071fd38301b67be76d1a (patch) | |
| tree | 21f02e67dda7a0fe13e4fc33b03ceaeb4157454d /meson.build | |
| parent | 7f1cab9c628a798ae2607940993771e6300e9e00 (diff) | |
| download | qemu-87ab88025247b893aad5071fd38301b67be76d1a.zip qemu-87ab88025247b893aad5071fd38301b67be76d1a.tar.gz qemu-87ab88025247b893aad5071fd38301b67be76d1a.tar.bz2 | |
block: Fix in_flight leak in request padding error path
When bdrv_pad_request() fails in bdrv_co_preadv_part(), bs->in_flight
has been increased, but is never decreased again. This leads to a hang
when trying to drain the block node.
This bug was observed with Windows guests which issue a request that
fully uses IOV_MAX during installation, so that when padding is
necessary (O_DIRECT with a 4k sector size block device on the host),
adding another entry causes failure.
Call bdrv_dec_in_flight() to fix this. There is a larger problem to
solve here because this request shouldn't even fail, but Windows doesn't
seem to care and with this minimal fix the installation succeeds. So
given that we're already in freeze, let's take this minimal fix for 6.1.
Fixes: 98ca45494fcd6bf0336ecd559e440b6de6ea4cd3
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1972079
Reported-by: Qing Wang <qinwang@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Message-Id: <20210727154923.91067-1-kwolf@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'meson.build')
0 files changed, 0 insertions, 0 deletions