From: "Huang, Kai" <kai.huang@intel.com>
To: "jarkko@kernel.org" <jarkko@kernel.org>,
"x86@kernel.org" <x86@kernel.org>, "bp@alien8.de" <bp@alien8.de>,
"lirongqing@baidu.com" <lirongqing@baidu.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"tglx@kernel.org" <tglx@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/sgx: Fix SRCU list traversal
Date: Wed, 11 Feb 2026 10:38:53 +0000 [thread overview]
Message-ID: <4adb6d4704e678e2d28b840ceaa7eda74cfac6ee.camel@intel.com> (raw)
In-Reply-To: <20260205015357.3635-1-lirongqing@baidu.com>
On Wed, 2026-02-04 at 20:53 -0500, lirongqing wrote:
> From: Li RongQing <lirongqing@baidu.com>
>
> Replace list_for_each_entry_rcu() with list_for_each_entry_srcu()
> when traversing the encl->mm_list protected by SRCU. This ensures
> proper synchronization annotation and avoids potential lockdep
> warnings about incorrect RCU usage.
>
> The list is protected by encl->srcu, not RCU, so the SRCU-specific
> iterator with srcu_read_lock_held() annotation is required.
>
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
Acked-by: Kai Huang <kai.huang@intel.com>
next prev parent reply other threads:[~2026-02-11 10:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 1:53 [PATCH] x86/sgx: Fix SRCU list traversal lirongqing
2026-02-05 17:58 ` Dave Hansen
2026-02-05 21:15 ` 答复: [外部邮件] " Li,Rongqing
2026-02-11 10:38 ` Huang, Kai [this message]
2026-02-24 0:30 ` Li,Rongqing(ACG CCN)
2026-02-24 1:14 ` Dave Hansen
2026-02-24 2:51 ` 答复: " Li,Rongqing(ACG CCN)
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=4adb6d4704e678e2d28b840ceaa7eda74cfac6ee.camel@intel.com \
--to=kai.huang@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--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