From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Security subsystem changes for v5.6
Date: Wed, 29 Jan 2020 08:24:55 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.2001290823510.4816@namei.org> (raw)
Just one minor fix this time. Please pull.
The following changes since commit 219d54332a09e8d8741c1e1982f5eae56099de85:
Linux 5.4 (2019-11-24 16:32:01 -0800)
are available in the Git repository at:
git://git.kernel.org:/pub/scm/linux/kernel/git/jmorris/linux-security for-v5.6
for you to fetch changes up to 10c2d111c906599942efd13109061885631c4a0c:
security: remove EARLY_LSM_COUNT which never used (2020-01-27 11:19:41 -0800)
----------------------------------------------------------------
Alex Shi (1):
security: remove EARLY_LSM_COUNT which never used
security/security.c | 1 -
1 file changed, 1 deletion(-)
---
commit 10c2d111c906599942efd13109061885631c4a0c
Author: Alex Shi <alex.shi@linux.alibaba.com>
Date: Tue Jan 21 16:50:03 2020 +0800
security: remove EARLY_LSM_COUNT which never used
This macro is never used from it was introduced in commit e6b1db98cf4d5
("security: Support early LSMs"), better to remove it.
Signed-off-by: Alex Shi <alex.shi@linux.alibaba.com>
Acked-by: Serge Hallyn <serge@hallyn.com>
Signed-off-by: James Morris <jmorris@namei.org>
diff --git a/security/security.c b/security/security.c
index 1bc000f834e2..344bf1327d7e 100644
--- a/security/security.c
+++ b/security/security.c
@@ -33,7 +33,6 @@
/* How many LSMs were built into the kernel? */
#define LSM_COUNT (__end_lsm_info - __start_lsm_info)
-#define EARLY_LSM_COUNT (__end_early_lsm_info - __start_early_lsm_info)
struct security_hook_heads security_hook_heads __lsm_ro_after_init;
static BLOCKING_NOTIFIER_HEAD(blocking_lsm_notifier_chain);
next reply other threads:[~2020-01-28 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 21:24 James Morris [this message]
2020-01-29 3:00 ` [GIT PULL] Security subsystem changes for v5.6 pr-tracker-bot
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.21.2001290823510.4816@namei.org \
--to=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox