[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3432701f63ea1a2904a1e84aa5db4b1bc0d4331c.camel@linux.ibm.com>
Date: Fri, 31 Jan 2025 11:59:29 -0500
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Roberto Sassu <roberto.sassu@...weicloud.com>, corbet@....net,
viro@...iv.linux.org.uk, brauner@...nel.org, jack@...e.cz,
dmitry.kasatkin@...il.com, eric.snowberg@...cle.com,
paul@...l-moore.com, jmorris@...ei.org, serge@...lyn.com
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org,
Roberto Sassu
<roberto.sassu@...wei.com>
Subject: Re: [PATCH v3 4/6] ima: Mark concurrent accesses to the iint
pointer in the inode security blob
On Wed, 2025-01-22 at 18:24 +0100, Roberto Sassu wrote:
> From: Roberto Sassu <roberto.sassu@...wei.com>
>
> Use the READ_ONCE() and WRITE_ONCE() macros to mark concurrent read and
> write accesses to the portion of the inode security blob containing the
> iint pointer.
>
> Writers are serialized by the iint lock.
>
> Reviewed-by: Mimi Zohar <zohar@...ux.ibm.com>
> Signed-off-by: Roberto Sassu <roberto.sassu@...wei.com>
Reviewed-by: Mimi Zohar <zohar@...ux.ibm.com>
Powered by blists - more mailing lists