From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fabian Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu] add patch fixing io_uring short read slow path
Date: Fri, 1 Jul 2022 13:53:39 +0200 [thread overview]
Message-ID: <c06aefdd-c0aa-2937-3907-52e70143c13e@proxmox.com> (raw)
In-Reply-To: <20220701083939.38155-1-f.ebner@proxmox.com>
How likely is this to trigger? Did you came across such events or is this a backport
for the sake of being cautious?
Mostly asking because 7.0 is already on staging, so it'd be good to know if we should
add another 6.0 release between (a bit of an hassle but possible due it not having yet
seen any public repo), or if there isn't as much time pressure and we can just roll it
out with the slower rollout of QEMU 7.0.
next prev parent reply other threads:[~2022-07-01 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 8:39 Fabian Ebner
2022-07-01 11:53 ` Thomas Lamprecht [this message]
2022-07-01 12:30 ` Fabian Ebner
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=c06aefdd-c0aa-2937-3907-52e70143c13e@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.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