From: "Huang, Kai" <kai.huang@intel.com>
To: "kas@kernel.org" <kas@kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"nik.borisov@suse.com" <nik.borisov@suse.com>,
"seanjc@google.com" <seanjc@google.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>
Cc: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"bp@alien8.de" <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Verma, Vishal L" <vishal.l.verma@intel.com>,
"tglx@kernel.org" <tglx@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] x86/virt/tdx: Fix lockdep assertion failure in cache flush for kexec
Date: Thu, 5 Mar 2026 21:35:53 +0000 [thread overview]
Message-ID: <51e221b9bcdeddffb95f2c39dcc285fb0e9f5951.camel@intel.com> (raw)
In-Reply-To: <4a15470a-5a10-4742-9faf-f66a88105d58@suse.com>
> >
> > The real requirement is tdx_cpu_flush_cache_for_kexec() must be done on
> > the same CPU. It's OK that it can be preempted in the middle as long as
> > it won't be rescheduled to another CPU.
>
> TLDR: It wants migration disabled.
Basically yes.
>
> >
> > Remove the too strong lockdep_assert_preemption_disabled(), and change
> > this_cpu_{read|write}() to __this_cpu_{read|write}() which provide the more
> > proper check (when CONFIG_DEBUG_PREEMPT is true), which checks all
> > conditions that the context cannot be moved to another CPU to run in the
> > middle.
> >
> > Fixes: 61221d07e815 ("KVM/TDX: Explicitly do WBINVD when no more TDX SEAMCALLs")
> > Cc: stable@vger.kernel.org
> > Reported-by: Vishal Verma <vishal.l.verma@intel.com>
> > Signed-off-by: Kai Huang <kai.huang@intel.com>
> > Tested-by: Vishal Verma <vishal.l.verma@intel.com>
>
>
> So how exactly does this patch prevent the BUG: printk in
> check_preemption_disabled from triggering, if the lockdep assert was
> triggering?
There's no real BUG here. It's just the
lockdep_assert_preemption_disabled() is misused.
next prev parent reply other threads:[~2026-03-05 21:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 10:22 [PATCH] x86/virt/tdx: Fix lockdep assertion failure in cache flush for kexec Kai Huang
2026-03-02 10:22 ` [PATCH v2] " Kai Huang
2026-03-02 10:26 ` Huang, Kai
2026-03-05 18:33 ` Nikolay Borisov
2026-03-05 21:35 ` Huang, Kai [this message]
2026-03-06 9:58 ` Nikolay Borisov
2026-03-08 10:12 ` Huang, Kai
2026-03-10 13:43 ` Sean Christopherson
2026-03-09 16:38 ` [PATCH] " Edgecombe, Rick P
2026-03-10 7:19 ` Huang, Kai
2026-03-10 13:50 ` Sean Christopherson
2026-03-10 16:36 ` Edgecombe, Rick P
2026-03-10 21:15 ` Huang, Kai
2026-03-10 16:42 ` Edgecombe, Rick P
-- strict thread matches above, loose matches on Subject: below --
2026-03-12 10:00 [PATCH v2] " Kai Huang
2026-03-16 12:14 ` Kiryl Shutsemau
2026-03-16 21:07 ` Huang, Kai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51e221b9bcdeddffb95f2c39dcc285fb0e9f5951.camel@intel.com \
--to=kai.huang@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nik.borisov@suse.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox