mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Casey Schaufler <casey@schaufler-ca.com>,
	john.johansen@canonical.com, mic@digikod.net
Cc: linux-security-module@vger.kernel.org, jmorris@namei.org,
	serge@hallyn.com, keescook@chromium.org,
	penguin-kernel@i-love.sakura.ne.jp,
	stephen.smalley.work@gmail.com, linux-kernel@vger.kernel.org,
	linux-api@vger.kernel.org
Subject: Re: [PATCH v12 0/11] LSM: Three basic syscalls
Date: Thu, 29 Jun 2023 22:14:42 -0400	[thread overview]
Message-ID: <f43449f878f629805d5de7fd06306741.paul@paul-moore.com> (raw)
In-Reply-To: <20230629195535.2590-1-casey@schaufler-ca.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

On Jun 29, 2023 Casey Schaufler <casey@schaufler-ca.com> wrote:
> 
> Add three system calls for the Linux Security Module ABI ...

I saw two small things (see patches 7/11 and 8/11) when looking at the
patchset today, but otherwise it looks pretty good to me.  However,
before I can merge this, at a minimum I would like to get an ACK from
John on the AppArmor patch; an ACK or a Reviewed-by on the rest of the
patchset would be great too.  I know Mickaël has reviewed and commented
on this patchset before, it would be nice if we could get his
ACK/Reviewed-by too.  Of course reviews and comments are always welcome
from anyone who has looked over the code; this is an important patchset
so the more eyes the better.

Assuming no one catches anything further, I think we can get this into
the lsm/next branch as soon as the merge window closes.

Thanks for all your work on this Casey.

--
paul-moore.com

      parent reply	other threads:[~2023-06-30  2:15 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230629195535.2590-1-casey.ref@schaufler-ca.com>
2023-06-29 19:55 ` [PATCH v12 00/11] " Casey Schaufler
2023-06-29 19:55   ` [PATCH v12 01/11] LSM: Identify modules by more than name Casey Schaufler
2023-07-11 15:35     ` Mickaël Salaün
2023-06-29 19:55   ` [PATCH v12 02/11] LSM: Maintain a table of LSM attribute data Casey Schaufler
2023-07-11 15:35     ` Mickaël Salaün
2023-07-14 19:42       ` Casey Schaufler
2023-07-21 21:40         ` Paul Moore
2023-06-29 19:55   ` [PATCH v12 03/11] proc: Use lsmids instead of lsm names for attrs Casey Schaufler
2023-07-11 15:36     ` Mickaël Salaün
2023-06-29 19:55   ` [PATCH v12 04/11] LSM: syscalls for current process attributes Casey Schaufler
2023-07-11 15:36     ` Mickaël Salaün
2023-07-14 21:59       ` Casey Schaufler
2023-07-21 22:28       ` Paul Moore
2023-07-30 22:34         ` Casey Schaufler
2023-06-29 19:55   ` [PATCH v12 05/11] LSM: Create lsm_list_modules system call Casey Schaufler
2023-07-11 15:36     ` Mickaël Salaün
2023-07-14 22:10       ` Casey Schaufler
2023-06-29 19:55   ` [PATCH v12 06/11] LSM: wireup Linux Security Module syscalls Casey Schaufler
2023-07-11 15:37     ` Mickaël Salaün
2023-06-29 19:55   ` [PATCH v12 07/11] LSM: Helpers for attribute names and filling lsm_ctx Casey Schaufler
2023-06-30  2:14     ` [PATCH v12 7/11] " Paul Moore
2023-06-30 17:11       ` Casey Schaufler
2023-06-30 18:23         ` Paul Moore
2023-06-29 19:55   ` [PATCH v12 08/11] Smack: implement setselfattr and getselfattr hooks Casey Schaufler
2023-06-30  2:14     ` [PATCH v12 8/11] " Paul Moore
2023-06-30 17:10       ` Casey Schaufler
2023-06-29 19:55   ` [PATCH v12 09/11] AppArmor: Add selfattr hooks Casey Schaufler
2023-06-29 19:55   ` [PATCH v12 10/11] SELinux: " Casey Schaufler
2023-07-11 15:37     ` Mickaël Salaün
2023-06-29 19:55   ` [PATCH v12 11/11] LSM: selftests for Linux Security Module syscalls Casey Schaufler
2023-07-11 18:16     ` Mickaël Salaün
2023-06-30  2:14   ` Paul Moore [this message]

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=f43449f878f629805d5de7fd06306741.paul@paul-moore.com \
    --to=paul@paul-moore.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=penguin-kernel@i-love.sakura.ne.jp \
    --cc=serge@hallyn.com \
    --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®