Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1641228 > unrolled thread

Re: [PATCH v3] LSM: Enable multiple calls to security_add_hooks() for the same LSM

Started byJames Morris <jmorris@namei.org>
First post2017-05-15 02:00 +0200
Last post2017-05-15 02:00 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v3] LSM: Enable multiple calls to security_add_hooks()  for the same LSM James Morris <jmorris@namei.org> - 2017-05-15 02:00 +0200

#1641228 — Re: [PATCH v3] LSM: Enable multiple calls to security_add_hooks() for the same LSM

FromJames Morris <jmorris@namei.org>
Date2017-05-15 02:00 +0200
SubjectRe: [PATCH v3] LSM: Enable multiple calls to security_add_hooks() for the same LSM
Message-ID<tHbAB-82-5@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

On Wed, 10 May 2017, Mickaël Salaün wrote:

> The commit d69dece5f5b6 ("LSM: Add /sys/kernel/security/lsm") extend
> security_add_hooks() with a new parameter to register the LSM name,
> which may be useful to make the list of currently loaded LSM available
> to userspace. However, there is no clean way for an LSM to split its
> hook declarations into multiple files, which may reduce the mess with
> all the included files (needed for LSM hook argument types) and make the
> source code easier to review and maintain.
> 
> This change allows an LSM to register multiple times its hook while
> keeping a consistent list of LSM names as described in
> Documentation/security/LSM.txt . The list reflects the order in which
> checks are made. This patch only check for the last registered LSM. If
> an LSM register multiple times its hooks, interleaved with other LSM
> registrations (which should not happen), its name will still appear in
> the same order that the hooks are called, hence multiple times.
> 
> To sum up, "capability,selinux,foo,foo" will be replaced with
> "capability,selinux,foo", however "capability,foo,selinux,foo" will
> remain as is.

Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next


-- 
James Morris
<jmorris@namei.org>

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web