[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d95c06e5-60e7-4adb-896f-5c99e7f4db52@linux.microsoft.com>
Date: Wed, 4 Oct 2023 19:49:13 -0700
From: Fan Wu <wufan@...ux.microsoft.com>
To: Eric Biggers <ebiggers@...nel.org>
Cc: corbet@....net, zohar@...ux.ibm.com, jmorris@...ei.org,
serge@...lyn.com, tytso@....edu, axboe@...nel.dk, agk@...hat.com,
snitzer@...nel.org, eparis@...hat.com, paul@...l-moore.com,
linux-doc@...r.kernel.org, linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-fscrypt@...r.kernel.org, linux-block@...r.kernel.org,
dm-devel@...hat.com, audit@...r.kernel.org,
roberto.sassu@...wei.com, linux-kernel@...r.kernel.org,
Deven Bowers <deven.desai@...ux.microsoft.com>
Subject: Re: [RFC PATCH v11 15/19] fsverity: consume builtin signature via LSM
hook
On 10/4/2023 7:27 PM, Eric Biggers wrote:
> On Wed, Oct 04, 2023 at 03:09:42PM -0700, Fan Wu wrote:
>> +#ifdef CONFIG_FS_VERITY_BUILTIN_SIGNATURES
>> +static int fsverity_inode_setsecurity(struct inode *inode,
>> + struct fsverity_descriptor *desc)
>> +{
>> + return security_inode_setsecurity(inode, FS_VERITY_INODE_SEC_NAME,
>> + desc->signature,
>> + le32_to_cpu(desc->sig_size), 0);
>> +}
>
> Why isn't the type of the second argument 'const struct fsverity_descriptor *'?
>
> - Eric
Thanks for the suggestion. I agree that adding 'const' here is a better
approach. I will update this in the next version.
-Fan
Powered by blists - more mailing lists