[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <46fb037b-0ee7-4d30-b690-9bdfbb38aa00@broadcom.com>
Date: Tue, 25 Jun 2024 08:01:08 -0700
From: Alexey Makhalov <alexey.makhalov@...adcom.com>
To: Borislav Petkov <bp@...en8.de>
Cc: linux-kernel@...r.kernel.org, virtualization@...ts.linux.dev,
hpa@...or.com, dave.hansen@...ux.intel.com, mingo@...hat.com,
tglx@...utronix.de, x86@...nel.org, ajay.kaher@...adcom.com,
bcm-kernel-feedback-list@...adcom.com, Alex James <alex.james@...adcom.com>
Subject: Re: [PATCH] x86/vmware: fix panic in vmware_hypercall_slow()
On 6/25/24 7:51 AM, Borislav Petkov wrote:
> On Tue, Jun 25, 2024 at 07:45:50AM -0700, Alexey Makhalov wrote:
>> My test environment was screwed up during the last version of the patchset.
>> I was using a kernel which was built previously and didn't pay attention to
>> commit hash suffix in `uname -r`.
>> Human mistake, apologize for that.
>
> Ok, no worries, happens.
>
>> Alex found it while doing TDX testing on x86/vmware on tip.
>>
>> Do you want me to resubmit the patchset to do not brake a git bisect?
>
> Nah, I'll fold it into the broken patch and rebase.
Thanks for your time.
>
> Btw, pls do me a favor and do not top-post but put your reply underneath the
> quoted text, like we all do.
Noted.
>
> Thx.
>
Powered by blists - more mailing lists