[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Xenvif non-zero byte assertion error during teardown
- To: Tu Dinh <ngoc-tu.dinh@xxxxxxxxxx>, win-pv-devel <win-pv-devel@xxxxxxxxxxxxxxxxxxxx>
- From: "Durrant, Paul" <pdurrant@xxxxxxxxxxxx>
- Date: Mon, 6 Jul 2026 14:19:49 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=amazon.co.uk; dmarc=pass action=none header.from=amazon.co.uk; dkim=pass header.d=amazon.co.uk; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:MIME-Version; bh=mfrpLrQF4bXvTworCQbJ1wDfTIPB7em0MAGEruNRahE=; b=YYwYCMGN+LpF4Hb4uf83dELwsPZIxnKal3iZHK5pZ1Hn4hk/X8pnMG85lHUzznuK+kH96/9lh+3ygAL9Wo8JLD7vP4KsYyIWqcW+euWLK+M8K3yPu8Msu1/ACW5t45vtUxYz/t5AtdafhqwvwJTdrWXbOkp9lM08ZnRs/0UYfh6a4i2FUhEeR9g99Mt7PVgkGGCrjukChgInpxEAvBxOrO9b/hiDCy4DS641+/FhP1tDu6ruB9JbULi1UmBbA8cLpdAH1kDwtUZ81EXkGcHfiIo16Vj2E7O8IM4D2aIyhY+PV78wB7cEGBaFnIA+RrySx7SbmGVBJ+Gh5gF+w5t29A==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=Sfg2LGMacGQ+9YYGjjGqm9onkYt4NlLLcX7hI3RMdbEZz+xpYmCfGWnHn0PFNViAW4SIDOwhj3Ine1LyXdDi2rSGNm6ynEGR7Gw6WetMrlxTEszA99LimLBGN1N4WL8GtuA5cFtBek3qGBMt4CVcu4JGxh6V7yYK43gLRPkiezn2TPq7zGVgENiXK6eOifwfQVLoHwJ6MopdZ8b7tLlq/NPpFiUOUfLyAi4vrS3AVvLraCX7bCQ5xxWNupaH5G2upEdBKOAbbeWYHVTilakvauQxV0Dw96XNwlEQBVDr2OcVpRbyKSYMOO3Soz8kX87BcQPC+titcUtswj37CqQ3qw==
- Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=amazoncorp2 header.d=amazon.co.uk header.i="@amazon.co.uk" header.h="From:To:Date:Message-ID:References:In-Reply-To:Content-ID:Content-Transfer-Encoding:MIME-Version:Subject"
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=amazon.co.uk;
- Delivery-date: Mon, 06 Jul 2026 14:20:01 +0000
- List-id: Developer list for the Windows PV Drivers subproject <win-pv-devel.lists.xenproject.org>
- Msip_labels: MSIP_Label_19e68092-05df-4271-8e3e-b2a4c82ba797_Enabled=true;MSIP_Label_19e68092-05df-4271-8e3e-b2a4c82ba797_SetDate=2026-07-06T14:17:16Z;MSIP_Label_19e68092-05df-4271-8e3e-b2a4c82ba797_ContentBits=0;MSIP_Label_19e68092-05df-4271-8e3e-b2a4c82ba797_Enabled=true;MSIP_Label_19e68092-05df-4271-8e3e-b2a4c82ba797_Tag=50, 3, 0, 1;MSIP_Label_19e68092-05df-4271-8e3e-b2a4c82ba797_Name=Confidential;MSIP_Label_19e68092-05df-4271-8e3e-b2a4c82ba797_ActionId=8618246d-bdf7-4aaf-9fd4-80971e6c98ae;MSIP_Label_19e68092-05df-4271-8e3e-b2a4c82ba797_SiteId=5280104a-472d-4538-9ccf-1e1d0efe8b1b;MSIP_Label_19e68092-05df-4271-8e3e-b2a4c82ba797_Method=Standard;
- Thread-index: AQHdCyKfsJpOQb/qzkKKIpiudCPyjLZgMtKAgAAJkgCAABLIgIAAPJgAgAATu4A=
- Thread-topic: Xenvif non-zero byte assertion error during teardown
> Doing so is hard since padding is architecture-dependent, and gets
> complex fast once child structures are involved. Some structures like
> INTERFACE (part of DebugInterface/SuspendInterface/etc) have padding
> that we can't simply eliminate or make explicit.
Ok, yes, I can see those would be hard.
I'm curious as to why this padding is suddenly a problem after a decade without
any issues though. Is it an issue with a newer toolchain?
|
