From: Serge Hallyn <serge@hallyn.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: paul@paul-moore.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
Subject: Re: [PATCH v10 07/11] LSM: Helpers for attribute names and filling lsm_ctx
Date: Thu, 15 Jun 2023 08:27:02 -0500 [thread overview]
Message-ID: <ZIsRptm9BmjtYQEA@jerom> (raw)
In-Reply-To: <20230428203417.159874-8-casey@schaufler-ca.com>
On Fri, Apr 28, 2023 at 01:34:13PM -0700, Casey Schaufler wrote:
> Add lsm_name_to_attr(), which translates a text string to a
> LSM_ATTR value if one is available.
>
> Add lsm_fill_user_ctx(), which fills a struct lsm_ctx, including
> the trailing attribute value. The .len value is padded to a multiple
> of 64 bits for alignment.
>
> All are used in module specific components of LSM system calls.
>
> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
(I assume you have a patch queued up for the undefined errors?)
next prev parent reply other threads:[~2023-06-15 13:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230428203417.159874-1-casey.ref@schaufler-ca.com>
2023-04-28 20:34 ` [PATCH v10 00/11] LSM: Three basic syscalls Casey Schaufler
2023-04-28 20:34 ` [PATCH v10 01/11] LSM: Identify modules by more than name Casey Schaufler
2023-04-28 20:34 ` [PATCH v10 02/11] LSM: Maintain a table of LSM attribute data Casey Schaufler
2023-04-28 20:34 ` [PATCH v10 03/11] proc: Use lsmids instead of lsm names for attrs Casey Schaufler
2023-06-13 18:35 ` Serge Hallyn
2023-04-28 20:34 ` [PATCH v10 04/11] LSM: syscalls for current process attributes Casey Schaufler
2023-06-07 22:32 ` [PATCH v10 4/11] " Paul Moore
2023-06-07 23:26 ` Casey Schaufler
2023-06-13 18:54 ` [PATCH v10 04/11] " Serge Hallyn
2023-04-28 20:34 ` [PATCH v10 05/11] LSM: Create lsm_list_modules system call Casey Schaufler
2023-06-13 19:02 ` Serge Hallyn
2023-04-28 20:34 ` [PATCH v10 06/11] LSM: wireup Linux Security Module syscalls Casey Schaufler
2023-04-28 20:34 ` [PATCH v10 07/11] LSM: Helpers for attribute names and filling lsm_ctx Casey Schaufler
2023-04-29 1:06 ` kernel test robot
2023-04-29 2:37 ` kernel test robot
2023-06-07 22:32 ` [PATCH v10 7/11] " Paul Moore
2023-06-15 13:19 ` [PATCH v10 07/11] " Serge Hallyn
2023-06-15 13:27 ` Serge Hallyn [this message]
2023-04-28 20:34 ` [PATCH v10 08/11] Smack: implement setselfattr and getselfattr hooks Casey Schaufler
2023-06-15 15:29 ` Serge Hallyn
2023-04-28 20:34 ` [PATCH v10 09/11] AppArmor: Add selfattr hooks Casey Schaufler
2023-04-28 20:34 ` [PATCH v10 10/11] SELinux: " Casey Schaufler
2023-06-07 22:32 ` Paul Moore
2023-06-07 23:39 ` Casey Schaufler
2023-04-28 20:34 ` [PATCH v10 11/11] LSM: selftests for Linux Security Module syscalls Casey Schaufler
2023-04-28 20:26 [PATCH v10 00/11] LSM: Three basic syscalls Casey Schaufler
2023-04-28 20:26 ` [PATCH v10 07/11] LSM: Helpers for attribute names and filling lsm_ctx 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=ZIsRptm9BmjtYQEA@jerom \
--to=serge@hallyn.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-api@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;
as well as URLs for NNTP newsgroup(s).