From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id D850C1FF137 for ; Tue, 17 Feb 2026 13:10:27 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2AE8E35853; Tue, 17 Feb 2026 13:11:18 +0100 (CET) Message-ID: Date: Tue, 17 Feb 2026 13:11:13 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [pve-devel] [PATCH qemu 2/2] fix #7197: add fix to avoid misaligned BLKZEROOUT casuing a hard error To: Proxmox VE development discussion , Fiona Ebner References: <20260112155940.298273-1-f.ebner@proxmox.com> <20260112155940.298273-3-f.ebner@proxmox.com> Content-Language: en-US From: Friedrich Weber In-Reply-To: <20260112155940.298273-3-f.ebner@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1771330267095 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.012 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: MSCLMXL2WO75LDONEQZ3WA4RWXUEGV2M X-Message-ID-Hash: MSCLMXL2WO75LDONEQZ3WA4RWXUEGV2M X-MailFrom: f.weber@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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.