From: Friedrich Weber <f.weber@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH kernel] cherry-pick fix for problematic CIFS/io_uring interaction
Date: Wed, 14 Jan 2026 17:18:04 +0100 [thread overview]
Message-ID: <28786a3c-1da1-4e92-8697-5eca5278743b@proxmox.com> (raw)
In-Reply-To: <20251006092428.756414-1-f.ebner@proxmox.com>
On 06/10/2025 11:24, Fiona Ebner wrote:
> When io_uring is used in the same task as CIFS, there might be
> unnecessary reconnects, which QEMU will treat as an IO error.
>
> This has been a long-standing issue [0] and was partially mitigated by
> qemu-server commit e31762f2 ("fix #4099: disable io_uring for virtual
> disks on CIFS storages"). However, back then it was not clear that
> it's enough to have IO via io_uring and IO via CIFS be present in the
> same task, even if io_uring is not used for CIFS. The issue resurfaced
> when QEMU blockdev mirroring was used with the source side using
> io_uring and the target being CIFS. This was reported by Aaron
> Lauterer and Friedrich Weber. It's also enough to have a VM with two
> disks, one using io_uring and one using CIFS and doing IO on both, to
> trigger the issue.
>
> Fix the issue by picking up the accepted fix from upstream, i.e.
> kernel commit 00be6f26a2a7 ("smb: client: transport: avoid reconnects
> triggered by pending task work").
>
> [0]: https://bugzilla.proxmox.com/show_bug.cgi?id=4099
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
I noticed the patch was backported to Ubuntu-6.17.0-14.14 as
0d83d11f144a, and is thus contained in our kernel >= 6.17.9-1.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2026-01-14 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 9:24 Fiona Ebner
2026-01-14 16:18 ` Friedrich Weber [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=28786a3c-1da1-4e92-8697-5eca5278743b@proxmox.com \
--to=f.weber@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.