From: jmorris@namei.org (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v1] LSM: Enable multiple calls to security_add_hooks() for the same LSM
Date: Mon, 1 May 2017 09:28:52 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1705010926080.12672@namei.org> (raw)
In-Reply-To: <20170429190257.27137-1-mic@digikod.net>
On Sat, 29 Apr 2017, Micka?l Sala?n wrote:
> Check if the registering LSM already registered hooks just before. This
> enable to split hook declarations into multiple files without
> registering multiple time the same LSM name, starting from commit
> d69dece5f5b6 ("LSM: Add /sys/kernel/security/lsm").
Please include a detailed rationale for these patches. The above tells us
very little about why they are needed.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2017-04-30 23:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 19:02 [PATCH v1] LSM: Enable multiple calls to security_add_hooks() for the same LSM Mickaël Salaün
2017-04-29 20:00 ` Casey Schaufler
2017-04-30 2:11 ` Tetsuo Handa
2017-04-30 9:35 ` Mickaël Salaün
2017-04-30 23:28 ` James Morris [this message]
[not found] ` <ca662813-e078-c579-d5a8-46ea03542f4b@digikod.net>
2017-05-08 20:07 ` 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=alpine.LRH.2.20.1705010926080.12672@namei.org \
--to=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox