[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjEwfcj6DWWh8mKr+O4ospkfNSC1GAvAcwfWAUAyTRq5A@mail.gmail.com>
Date: Fri, 6 Feb 2026 15:08:29 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Josh Poimboeuf <jpoimboe@...nel.org>, Paolo Bonzini <pbonzini@...hat.com>
Cc: Thomas Gleixner <tglx@...-um.de>, Thorsten Leemhuis <regressions@...mhuis.info>,
Alexey Makhalov <alexey.makhalov@...adcom.com>, x86@...nel.org, linux-kernel@...r.kernel.org,
Ajay Kaher <ajay.kaher@...adcom.com>, bcm-kernel-feedback-list@...adcom.com,
Peter Zijlstra <peterz@...radead.org>, Justin Forbes <jforbes@...oraproject.org>,
Linux kernel regressions list <regressions@...ts.linux.dev>
Subject: Re: [PATCH] x86/vmware: Fix hypercall clobbers
On Fri, 6 Feb 2026 at 14:38, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> I'm going to change that commit message to make it clear that it's a
> QEMU bug, plain and simple. There's no point in claiming this fixes a
> kernel bug when it's a pure workaround for a bug elsewhere.
I have created an issue at gitlab:
https://gitlab.com/qemu-project/qemu/-/issues/3293
and hopefully this will get fixed in QEMU at some point.
Adding Paolo to the participants, since he presumably knows what to do
with qemu, since he touched that qemu file a couple of months ago.
(The fix looks trivial, as suggested by Alexey: just change the
"uint32_t data[6];" to use target_ulong instead of uint32_t, but
somebody needs to test it and maybe qemu has other rules for register
types)
Linus
Powered by blists - more mailing lists