[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f3f08ce6b3b273bde1ce6eb41b0ca3c0@paul-moore.com>
Date: Tue, 05 Dec 2023 16:25:26 -0500
From: Paul Moore <paul@...l-moore.com>
To: "Seth Forshee (DigitalOcean)" <sforshee@...nel.org>,
Christian Brauner <brauner@...nel.org>,
Serge Hallyn <serge@...lyn.com>,
Eric Paris <eparis@...hat.com>,
James Morris <jmorris@...ei.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
Miklos Szeredi <miklos@...redi.hu>,
Amir Goldstein <amir73il@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-security-module@...r.kernel.org, audit@...r.kernel.org,
linux-unionfs@...r.kernel.org,
"Seth Forshee (DigitalOcean)" <sforshee@...nel.org>
Subject: Re: [PATCH 3/16] capability: rename cpu_vfs_cap_data to vfs_caps
On Nov 29, 2023 "Seth Forshee (DigitalOcean)" <sforshee@...nel.org> wrote:
>
> vfs_caps is a more generic name which is better suited to the broader
> use this struct will see in subsequent commits.
>
> Signed-off-by: Seth Forshee (DigitalOcean) <sforshee@...nel.org>
> Reviewed-by: Christian Brauner <brauner@...nel.org>
> ---
> include/linux/capability.h | 4 ++--
> kernel/auditsc.c | 4 ++--
> security/commoncap.c | 8 ++++----
> 3 files changed, 8 insertions(+), 8 deletions(-)
Bonus points in that the proposed name is shorter too :)
Technically you'll want to get Serge's ACK as he's the capabilities
maintainer, but with my LSM hat on this looks okay, and is pretty
trivial anyway.
Acked-by: Paul Moore <paul@...l-moore.com> (Audit,LSM)
--
paul-moore.com
Powered by blists - more mailing lists