From: Baolu Lu <baolu.lu@linux.intel.com>
To: Breno Leitao <leitao@debian.org>
Cc: Ido Schimmel <idosch@idosch.org>,
iommu@lists.linux.dev, dwmw2@infradead.org, tglx@linutronix.de,
peterz@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Suspicious RCU usage in enable_drhd_fault_handling()
Date: Fri, 17 Jan 2025 09:20:04 +0800 [thread overview]
Message-ID: <18804ca2-bb8f-46ae-8cce-4c4c3443e027@linux.intel.com> (raw)
In-Reply-To: <20250116-ludicrous-mature-ferret-8956dc@leitao>
On 1/16/25 21:34, Breno Leitao wrote:
> On Tue, Oct 29, 2024 at 09:15:55AM +0800, Baolu Lu wrote:
>> On 2024/10/28 16:43, Ido Schimmel wrote:
>>> Hi,
>>>
>>> I have recently enabled CONFIG_RCU_EXPERT and CONFIG_PROVE_RCU_LIST in
>>> our debug configuration file and started observing the following splat
>>> [1] on one of our machines during boot. Searched the archives, but did
>>> not find a similar report.
>>>
>>> Not sure what is the right fix as I am not familiar with this code, but
>>> I can easily test patches.
>> Thanks for reporting this issue. I've been able to reproduce it locally
>> and will work on a fix. I'll let you know as soon as I have an update.
> Have you had a chance to look at this problem? I am still seeing it in
> 6.13-rc7.
Yes. I have spent some time on this, but I haven't yet figured out a
simple way to fix it.
I tried to add the rcu lock or use the dmar_global_lock instead, but
neither proved successful. Perhaps it's time to reconsider the locking
scheme for those lists.
Thanks,
baolu
prev parent reply other threads:[~2025-01-17 1:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Zx9OwdLIc_VoQ0-a@shredder.mtl.com>
[not found] ` <a45ae593-20b0-4604-bf2e-2870b2c7f11a@linux.intel.com>
2025-01-16 13:34 ` Suspicious RCU usage in enable_drhd_fault_handling() Breno Leitao
2025-01-17 1:20 ` Baolu Lu [this message]
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=18804ca2-bb8f-46ae-8cce-4c4c3443e027@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=idosch@idosch.org \
--cc=iommu@lists.linux.dev \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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