From: Mimi Zohar <zohar@linux.ibm.com>
To: Breno Leitao <leitao@debian.org>,
Roberto Sassu <roberto.sassu@huawei.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
Eric Snowberg <eric.snowberg@oracle.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v2] ima: kexec: silence RCU list traversal warning
Date: Fri, 17 Jan 2025 18:37:52 -0500 [thread overview]
Message-ID: <c84b2a23b5ea5cc5332c6edcb0a953a0a9ecd4d4.camel@linux.ibm.com> (raw)
In-Reply-To: <20250116-jovial-stalwart-chipmunk-0b3693@leitao>
On Thu, 2025-01-16 at 03:23 -0800, Breno Leitao wrote:
> Hello Mimi,
>
> On Thu, Nov 21, 2024 at 01:57:12AM -0800, Breno Leitao wrote:
> > The ima_measurements list is append-only and doesn't require
> > rcu_read_lock() protection. However, lockdep issues a warning when
> > traversing RCU lists without the read lock:
> >
> > security/integrity/ima/ima_kexec.c:40 RCU-list traversed in non-reader
> > section!!
>
> What are the next steps in regarding this issue? I am still seeing this
> problem on Linus' tree.
It's included in the v6.14 pull request, which I just sent.
thanks,
Mimi
prev parent reply other threads:[~2025-01-17 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 9:57 [PATCH v2] ima: kexec: silence RCU list traversal warning Breno Leitao
2025-01-16 11:23 ` Breno Leitao
2025-01-17 23:37 ` Mimi Zohar [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=c84b2a23b5ea5cc5332c6edcb0a953a0a9ecd4d4.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dmitry.kasatkin@gmail.com \
--cc=ebiederm@xmission.com \
--cc=eric.snowberg@oracle.com \
--cc=jmorris@namei.org \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).