From: Casey Schaufler <casey@schaufler-ca.com>
To: Paul Moore <paul@paul-moore.com>
Cc: casey.schaufler@intel.com, linux-security-module@vger.kernel.org,
jmorris@namei.org, keescook@chromium.org,
john.johansen@canonical.com, penguin-kernel@i-love.sakura.ne.jp,
stephen.smalley.work@gmail.com, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, mic@digikod.net,
linux-fsdevel@vger.kernel.org, casey@schaufler-ca.com
Subject: Re: [PATCH v5 3/8] proc: Use lsmids instead of lsm names for attrs
Date: Wed, 11 Jan 2023 16:37:54 -0800 [thread overview]
Message-ID: <9b031aaa-08f8-3b99-64f8-a4ecadb3f7e8@schaufler-ca.com> (raw)
In-Reply-To: <CAHC9VhRwg8g--i1db9fkwOey5aU1b2-9nRBDRRzbYRRm_QVr6w@mail.gmail.com>
On 1/11/2023 1:01 PM, Paul Moore wrote:
> On Mon, Jan 9, 2023 at 1:09 PM Casey Schaufler <casey@schaufler-ca.com> wrote:
>> Use the LSM ID number instead of the LSM name to identify which
>> security module's attibute data should be shown in /proc/self/attr.
>> The security_[gs]etprocattr() functions have been changed to expect
>> the LSM ID. The change from a string comparison to an integer comparison
>> in these functions will provide a minor performance improvement.
>>
>> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
>> Cc: linux-fsdevel@vger.kernel.org
>> ---
>> fs/proc/base.c | 29 +++++++++++++++--------------
>> fs/proc/internal.h | 2 +-
>> include/linux/security.h | 11 +++++------
>> security/security.c | 11 +++++------
>> 4 files changed, 26 insertions(+), 27 deletions(-)
> ..
>
>> diff --git a/fs/proc/base.c b/fs/proc/base.c
>> index 9e479d7d202b..9328b6b07dfc 100644
>> --- a/fs/proc/base.c
>> +++ b/fs/proc/base.c
>> @@ -2837,27 +2838,27 @@ static const struct inode_operations proc_##LSM##_attr_dir_inode_ops = { \
>>
>> #ifdef CONFIG_SECURITY_SMACK
>> static const struct pid_entry smack_attr_dir_stuff[] = {
>> - ATTR("smack", "current", 0666),
>> + ATTR(LSM_ID_SMACK, "current", 0666),
>> };
>> LSM_DIR_OPS(smack);
>> #endif
>>
>> #ifdef CONFIG_SECURITY_APPARMOR
>> static const struct pid_entry apparmor_attr_dir_stuff[] = {
>> - ATTR("apparmor", "current", 0666),
>> - ATTR("apparmor", "prev", 0444),
>> - ATTR("apparmor", "exec", 0666),
>> + ATTR(LSM_ID_APPARMOR, "current", 0666),
>> + ATTR(LSM_ID_APPARMOR, "prev", 0444),
>> + ATTR(LSM_ID_APPARMOR, "exec", 0666),
>> };
>> LSM_DIR_OPS(apparmor);
>> #endif
>>
>> static const struct pid_entry attr_dir_stuff[] = {
>> - ATTR(NULL, "current", 0666),
>> - ATTR(NULL, "prev", 0444),
>> - ATTR(NULL, "exec", 0666),
>> - ATTR(NULL, "fscreate", 0666),
>> - ATTR(NULL, "keycreate", 0666),
>> - ATTR(NULL, "sockcreate", 0666),
>> + ATTR(0, "current", 0666),
>> + ATTR(0, "prev", 0444),
>> + ATTR(0, "exec", 0666),
>> + ATTR(0, "fscreate", 0666),
>> + ATTR(0, "keycreate", 0666),
>> + ATTR(0, "sockcreate", 0666),
> See the discussion in patch 1/8, we should use a macro instead of a 0
> here (although the exact macro definition is very much up for
> discussion):
>
> ATTR(LSM_ID_UNDEF, "current", 0666),
Or LSM_ID_NALSMID, or whatever. Agreed.
>
> --
> paul-moore.com
next prev parent reply other threads:[~2023-01-12 0:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230109180717.58855-1-casey.ref@schaufler-ca.com>
2023-01-09 18:07 ` [PATCH v5 0/8] LSM: Three basic syscalls Casey Schaufler
2023-01-09 18:07 ` [PATCH v5 1/8] LSM: Identify modules by more than name Casey Schaufler
2023-01-11 21:00 ` Paul Moore
2023-01-12 0:05 ` Casey Schaufler
2023-01-12 20:30 ` Paul Moore
2023-01-09 18:07 ` [PATCH v5 2/8] LSM: Maintain a table of LSM attribute data Casey Schaufler
2023-01-11 1:58 ` kernel test robot
2023-01-11 21:01 ` Paul Moore
2023-01-12 0:36 ` Casey Schaufler
2023-01-12 20:26 ` Paul Moore
2023-01-09 18:07 ` [PATCH v5 3/8] proc: Use lsmids instead of lsm names for attrs Casey Schaufler
2023-01-11 21:01 ` Paul Moore
2023-01-12 0:37 ` Casey Schaufler [this message]
2023-01-09 18:07 ` [PATCH v5 4/8] LSM: lsm_get_self_attr syscall for LSM self attributes Casey Schaufler
2023-01-11 21:07 ` Paul Moore
2023-01-12 1:37 ` Casey Schaufler
2023-01-12 21:37 ` Paul Moore
2023-01-12 14:40 ` Arnd Bergmann
2023-01-12 21:39 ` Paul Moore
2023-02-14 16:48 ` Mickaël Salaün
2023-02-02 4:53 ` Serge Hallyn (shallyn)
2023-02-14 17:41 ` Mickaël Salaün
2023-02-14 18:06 ` Casey Schaufler
2023-01-09 18:07 ` [PATCH v5 5/8] LSM: Create lsm_module_list system call Casey Schaufler
2023-01-11 0:50 ` kernel test robot
2023-01-11 21:07 ` Paul Moore
2023-01-12 1:39 ` Casey Schaufler
2023-01-12 21:43 ` Paul Moore
2023-01-09 18:07 ` [PATCH v5 6/8] LSM: lsm_set_self_attr syscall for LSM self attributes Casey Schaufler
2023-01-09 18:07 ` [PATCH v5 7/8] LSM: wireup Linux Security Module syscalls Casey Schaufler
2023-01-13 9:31 ` Geert Uytterhoeven
2023-01-09 18:07 ` [PATCH v5 8/8] LSM: selftests for " Casey Schaufler
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=9b031aaa-08f8-3b99-64f8-a4ecadb3f7e8@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=casey.schaufler@intel.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=stephen.smalley.work@gmail.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®