From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Reiter <s.reiter@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-qemu 1/2] add upstream fixes for qmp_block_resize
Date: Tue, 30 Mar 2021 18:57:24 +0200 [thread overview]
Message-ID: <fcf988be-90b2-7038-2e3d-a086a9ccaf79@proxmox.com> (raw)
In-Reply-To: <20210330155952.16389-1-s.reiter@proxmox.com>
On 30.03.21 17:59, Stefan Reiter wrote:
> cherry-picked cleanly from 6.0 development tree, fixes an issue with
> resizing RBD drives (and reportedly also on krbd or potentially other
> storage backends) with iothreads.
>
> Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
> ---
>
> Reported here ff.:
> https://forum.proxmox.com/threads/all-vms-locking-up-after-latest-pve-update.85397/post-380409
>
> Posters could also reproduce this on krbd, for me it only occured on user-space
> rbd. Nevertheless, this looks to be a hot smoking gun, especially since both
> configs from the forum show iothread=1.
>
>
> ...lock-Fix-locking-in-qmp_block_resize.patch | 42 +++++++
> ...x-deadlock-in-bdrv_co_yield_to_drain.patch | 118 ++++++++++++++++++
> debian/patches/series | 2 +
> 3 files changed, 162 insertions(+)
> create mode 100644 debian/patches/extra/0011-block-Fix-locking-in-qmp_block_resize.patch
> create mode 100644 debian/patches/extra/0012-block-Fix-deadlock-in-bdrv_co_yield_to_drain.patch
>
>
applied, thanks!
prev parent reply other threads:[~2021-03-30 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 15:59 [pve-devel] " Stefan Reiter
2021-03-30 15:59 ` [pve-devel] [PATCH qemu-server 2/2] increase timeout for QMP block_resize Stefan Reiter
2021-03-30 16:57 ` Thomas Lamprecht
2021-03-30 16:57 ` [pve-devel] applied: " Thomas Lamprecht
2021-03-30 16:57 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fcf988be-90b2-7038-2e3d-a086a9ccaf79@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.reiter@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox