[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <34b72280-ab31-15a1-f37e-58eac34a0d37@huaweicloud.com>
Date: Sat, 10 Jun 2023 09:01:35 +0200
From: Roberto Sassu <roberto.sassu@...weicloud.com>
To: Jarkko Sakkinen <jarkko@...nel.org>,
Mengchi Cheng <mengcc@...zon.com>
Cc: miklos@...redi.hu, linux-unionfs@...r.kernel.org,
kamatam@...zon.com, yoonjaeh@...zon.com, zohar@...ux.ibm.com,
dmitry.kasatkin@...il.com, paul@...l-moore.com, jmorris@...ei.org,
serge@...lyn.com, stephen.smalley.work@...il.com,
eparis@...isplace.org, casey@...aufler-ca.com,
linux-kernel@...r.kernel.org, linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org, selinux@...r.kernel.org,
bpf@...r.kernel.org, kpsingh@...nel.org, keescook@...omium.org,
nicolas.bouchinet@...p-os.org,
Roberto Sassu <roberto.sassu@...wei.com>
Subject: Re: [PATCH v11 2/4] smack: Set the SMACK64TRANSMUTE xattr in
smack_inode_init_security()
On 6/9/2023 9:26 AM, Jarkko Sakkinen wrote:
> On Mon Jun 5, 2023 at 11:38 AM EEST, Roberto Sassu wrote:
>> On Sat, 2023-06-03 at 21:15 +0200, Roberto Sassu wrote:
>>> From: Roberto Sassu <roberto.sassu@...wei.com>
>>>
>>> With the newly added ability of LSMs to supply multiple xattrs, set
>>> SMACK64TRASMUTE in smack_inode_init_security(), instead of d_instantiate().
>
> nit: TRANSMUTE
>
> Sorry, just hit into my eye. I skimmed it because I implemented original
> feature :-)
Cool!
Currently the transmute xattr is defined as:
#define XATTR_SMACK_TRANSMUTE "SMACK64TRANSMUTE"
so, should be good to say the full xattr name, right?
Thanks
Roberto
Powered by blists - more mailing lists