From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] lsm/lsm-pr-20241004
Date: Fri, 04 Oct 2024 13:04:21 -0400 [thread overview]
Message-ID: <a68d32deab61b1c4b1be66e5346ef547@paul-moore.com> (raw)
Linus,
Here is the CONFIG_SECURITY_TOMOYO_LKM revert that we've been discussing
this week. With near unanimous agreement that the original TOMOYO
patches were not the right way to solve the distro problem Tetsuo is
trying the solve, reverting is our best option at this time.
Please merge for v6.12-rc2.
-Paul
--
The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:
Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git
tags/lsm-pr-20241004
for you to fetch changes up to c5e3cdbf2afedef77b64229fd0aed693abf0a0c4:
tomoyo: revert CONFIG_SECURITY_TOMOYO_LKM support
(2024-10-04 11:41:22 -0400)
----------------------------------------------------------------
lsm/stable-6.12 PR 20241004
----------------------------------------------------------------
Paul Moore (1):
tomoyo: revert CONFIG_SECURITY_TOMOYO_LKM support
security/tomoyo/Kconfig | 15 -
security/tomoyo/Makefile | 8
security/tomoyo/common.c | 14 -
security/tomoyo/common.h | 72 ------
security/tomoyo/gc.c | 3
security/tomoyo/init.c | 366 --------------------------------
security/tomoyo/load_policy.c | 12 -
security/tomoyo/proxy.c | 82 -------
security/tomoyo/securityfs_if.c | 10
security/tomoyo/tomoyo.c | 110 +++++++++
security/tomoyo/util.c | 3
11 files changed, 118 insertions(+), 577 deletions(-)
--
paul-moore.com
next reply other threads:[~2024-10-04 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 17:04 Paul Moore [this message]
2024-10-05 18:07 ` 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=a68d32deab61b1c4b1be66e5346ef547@paul-moore.com \
--to=paul@paul-moore.com \
--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
all inboxes | Powered by JetHome®