From: Cai Xinchen <caixinchen1@huawei.com>
To: Mimi Zohar <zohar@linux.ibm.com>, <roberto.sassu@huawei.com>,
<dmitry.kasatkin@gmail.com>, <eric.snowberg@oracle.com>,
<paul@paul-moore.com>, <jmorris@namei.org>, <serge@hallyn.com>,
<amir73il@gmail.com>
Cc: <linux-integrity@vger.kernel.org>,
<linux-security-module@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
<lujialin4@huawei.com>
Subject: Re: [PATCH] ima: initialize the real inode attributes of the iint cache
Date: Mon, 2 Nov 2026 20:09:23 +0800 [thread overview]
Message-ID: <faee04cc-fb04-4e56-bfe4-1eae5b819137@huawei.com> (raw)
In-Reply-To: <cb3ef53e2e5c6d74051528c2b9b9c0a294d6c119.camel@linux.ibm.com>
Hi Mimi. Thanks for review.
I mistakenly used integrity_inode_attrs_store. In the next version, I
will directly use
memset to initialize the real_inode structure.
I double checked b836c4d29f27. That commit also added real_ino and
real_dev to struct integrity_iinit_cache and started reading them in
process_measurement(). However, iinit_init_always() only reset
iint->version, leaving real_ino and real_dev stale. After 309e2b775da8,
these three variables are encapsulated into integrity_inode_attributes.
Therefore, I believe b836c4d29f27 is the appropriate Fixes tag. If I
have missed anything, please let me know.
On 11/2/2026 7:20 PM, Mimi Zohar wrote:
> Thanks, Cai.
>
> Instead of calling integrity_inode_attrs_store(), reset the entire real_inode
> structure. The store sets dev and ino to the stacked inode’s values, but at
> allocation time there are no valid real-inode attributes yet, so the fields
> should be cleared. The patch only works because the stacked and real inodes
> happen to be on different superblocks.
>
> The Fixes: tag looks wrong. In b836c4d29f27, real_inode is an unsigned long
> version and init_always() resets it fully.
next prev parent reply other threads:[~2026-11-02 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 2:47 Cai Xinchen
2026-11-02 11:20 ` Mimi Zohar
2026-11-02 12:09 ` Cai Xinchen [this message]
2026-11-02 15:03 ` Mimi Zohar
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=faee04cc-fb04-4e56-bfe4-1eae5b819137@huawei.com \
--to=caixinchen1@huawei.com \
--cc=amir73il@gmail.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=lujialin4@huawei.com \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=stable@vger.kernel.org \
--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®