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 qemu 2/2] fix #7197: add fix to avoid misaligned BLKZEROOUT casuing a hard error
Date: Tue, 17 Feb 2026 13:11:13 +0100 [thread overview]
Message-ID: <cbd85fc7-6d9e-4d8a-908b-df3427e4395b@proxmox.com> (raw)
In-Reply-To: <20260112155940.298273-3-f.ebner@proxmox.com>
On 12/01/2026 16:59, Fiona Ebner wrote:
> [...]
> +Commit 5634622bcb ("file-posix: allow BLKZEROOUT with -t writeback")
> +enables the BLKZEROOUT ioctl when using 'writeback' cache, regressing
> +certain 'qemu-img convert' invocations, because of a pre-existing
> +issue. Namely, the BLKZEROOUT ioctl might fail with errno EINVAL when
> +the request is shorter than the block size of the block device.
> +Fallback to the bounce buffer, similar to when the ioctl is not
> +supported at all, rather than treating such an error as fatal.
Ping -- this was now also reported in enterprise support.
next prev parent reply other threads:[~2026-02-17 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 15:59 [pve-devel] [PATCH-SERIES qemu 0/2] fix two completely different bugs both caused by non-aligned zero writes Fiona Ebner
2026-01-12 15:59 ` [pve-devel] [PATCH qemu 1/2] fix #7222: add fix for crash caused by zero write during sync drive mirror Fiona Ebner
2026-01-12 15:59 ` [pve-devel] [PATCH qemu 2/2] fix #7197: add fix to avoid misaligned BLKZEROOUT casuing a hard error Fiona Ebner
2026-02-17 12:11 ` Friedrich Weber [this message]
2026-02-05 12:06 ` [pve-devel] [PATCH-SERIES qemu 0/2] fix two completely different bugs both caused by non-aligned zero writes Fiona Ebner
2026-02-17 18:28 ` applied: " Thomas Lamprecht
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=cbd85fc7-6d9e-4d8a-908b-df3427e4395b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox