[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xenvif non-zero byte assertion error during teardown


  • To: "Durrant, Paul" <pdurrant@xxxxxxxxxxxx>, win-pv-devel <win-pv-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Tu Dinh <ngoc-tu.dinh@xxxxxxxxxx>
  • Date: Mon, 6 Jul 2026 16:23:29 +0200
  • Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=selector1 header.d=vates.tech header.i="@vates.tech" header.h="From:Subject:Date:Message-ID:To:MIME-Version:Content-Type:In-Reply-To:References:Feedback-ID"
  • Delivery-date: Mon, 06 Jul 2026 14:23:38 +0000
  • Feedback-id: default:8631fc262581453bbf619ec5b2062170:Sweego
  • List-id: Developer list for the Windows PV Drivers subproject <win-pv-devel.lists.xenproject.org>

On 06/07/2026 16:20, Durrant, Paul wrote:
>> 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?
> 

I did recently switch to VS2026 so that might be a reason. Or that it 
was rare enough to not be detected during typical runs of the debug build.


--
Ngoc Tu Dinh | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.