From: Roberto Sassu <roberto.sassu@huaweicloud.com>
To: Weibin Liu <liuwb@xiaopeng.com>, linux-integrity@vger.kernel.org
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, Mimi Zohar <zohar@linux.ibm.com>,
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>,
Steven Chen <chenste@linux.microsoft.com>,
stable@vger.kernel.org, Zhu Guanglei <zhugl3@xiaopeng.com>
Subject: Re: [PATCH v2] ima: fix races when deleting measurement list entries
Date: Mon, 09 Nov 2026 14:06:14 +0100 [thread overview]
Message-ID: <f5b2a9348436f0ac8a11fe1957174de5cbba495b.camel@huaweicloud.com> (raw)
In-Reply-To: <179422925743.761920.15976497107095793440@xiaopeng.com>
On Mon, 2026-11-09 at 21:00 +0800, Weibin Liu wrote:
> On Mon, 2026-11-09 at 13:49 +0100, Roberto Sassu wrote:
> > Is it still true with the new semaphore?
>
> No. That paragraph describes the unpatched code. The patch serializes
> writers with ima_measurements_rwsem and protects the lookup and cut
> with ima_extend_list_mutex.
Sorry, the comment was not in the right place. Is it still necessary
to take ima_extend_list_mutex to determine the cut position, since now
writers are serialized with the semaphore?
Roberto
prev parent reply other threads:[~2026-11-09 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 12:33 Weibin Liu
2026-11-09 12:49 ` Roberto Sassu
2026-11-09 13:00 ` Weibin Liu
2026-11-09 13:06 ` Roberto Sassu [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=f5b2a9348436f0ac8a11fe1957174de5cbba495b.camel@huaweicloud.com \
--to=roberto.sassu@huaweicloud.com \
--cc=chenste@linux.microsoft.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=liuwb@xiaopeng.com \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=stable@vger.kernel.org \
--cc=zhugl3@xiaopeng.com \
--cc=zohar@linux.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
all inboxes | Powered by JetHome®