From: Greg KH <gregkh@linuxfoundation.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: linux-security-module <linux-security-module@vger.kernel.org>,
Casey Schaufler <casey@schaufler-ca.com>,
KP Singh <kpsingh@kernel.org>, Paul Moore <paul@paul-moore.com>,
bpf <bpf@vger.kernel.org>, Kees Cook <keescook@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC PATCH 1/2] LSM: Allow dynamically appendable LSM modules.
Date: Wed, 27 Sep 2023 17:33:24 +0200 [thread overview]
Message-ID: <2023092740-psychic-debating-da77@gregkh> (raw)
In-Reply-To: <cc8e16bb-5083-01da-4a77-d251a76dc8ff@I-love.SAKURA.ne.jp>
On Thu, Sep 28, 2023 at 12:08:47AM +0900, Tetsuo Handa wrote:
> +extern int register_loadable_lsm(struct security_hook_list *hooks, int count,
> + const char *lsm);
naming nit, this should be "noun_verb" where ever possible to make it
easier to handle global symbols. So "lsm_register()" perhaps?
thanks,
greg k-h
next prev parent reply other threads:[~2023-09-27 15:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 15:08 [RFC PATCH 1/2] LSM: Allow dynamically appendable LSM modules Tetsuo Handa
2023-09-27 15:09 ` [RFC PATCH 2/2] LSM: A sample of dynamically appendable LSM module Tetsuo Handa
2023-09-27 16:05 ` Song Liu
2023-09-27 15:33 ` Greg KH [this message]
2023-09-27 16:02 ` [RFC PATCH 1/2] LSM: Allow dynamically appendable LSM modules KP Singh
2023-10-01 11:08 ` Tetsuo Handa
2023-10-01 14:43 ` KP Singh
2023-10-03 14:27 ` Tetsuo Handa
2023-10-03 15:09 ` KP Singh
2023-10-21 14:19 ` Tetsuo Handa
2023-10-21 15:20 ` KP Singh
2023-10-22 13:34 ` Tetsuo Handa
2023-10-03 23:27 ` Paul Moore
2023-10-03 23:41 ` KP Singh
2023-10-05 9:47 ` José Bollo
2023-10-05 13:59 ` Tetsuo Handa
2023-10-05 14:12 ` KP Singh
2023-09-27 16:37 ` Casey Schaufler
2023-10-01 11:31 ` Tetsuo Handa
2023-10-01 15:19 ` Casey Schaufler
2023-10-04 10:40 ` Tetsuo Handa
2023-10-04 10:48 ` Tetsuo Handa
2023-10-20 20:40 ` Casey Schaufler
2023-10-21 12:21 ` Tetsuo Handa
2023-10-01 15:44 ` Kees Cook
2023-10-02 10:04 ` Tetsuo Handa
2023-10-02 17:05 ` Kees Cook
2023-10-03 23:39 ` Paul Moore
2023-10-05 10:48 ` Tetsuo Handa
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=2023092740-psychic-debating-da77@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bpf@vger.kernel.org \
--cc=casey@schaufler-ca.com \
--cc=keescook@chromium.org \
--cc=kpsingh@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.