From: "Huang, Kai" <kai.huang@intel.com>
To: "pbonzini@redhat.com" <pbonzini@redhat.com>,
"nik.borisov@suse.com" <nik.borisov@suse.com>,
"kas@kernel.org" <kas@kernel.org>,
"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>,
"Verma, Vishal L" <vishal.l.verma@intel.com>,
"tglx@kernel.org" <tglx@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] x86/virt/tdx: Fix lockdep assertion failure in cache flush for kexec
Date: Sun, 8 Mar 2026 10:12:13 +0000 [thread overview]
Message-ID: <5de759b3bfba98c26c4fdd413bdfc2b196cb2b87.camel@intel.com> (raw)
In-Reply-To: <2db61bc6-813d-468a-8ded-018dc9dfb0cf@suse.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.
>
> Essentially in check_preemption_disabled() the check is considered
> passed IF ANY of the preempt disable conditions is met, i.e it's more
> laxed. So yeah, makes sense!
>
> Reviewed-by: Nikolay Borisov <nik.borisov@suse.com>
Thanks!
next prev parent reply other threads:[~2026-03-08 10:12 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
2026-03-06 9:58 ` Nikolay Borisov
2026-03-08 10:12 ` Huang, Kai [this message]
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=5de759b3bfba98c26c4fdd413bdfc2b196cb2b87.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