From: Greg KH <greg@kroah.com>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org, linux-security-module@wirex.com
Subject: [BK PATCH] LSM changes for 2.5.52
Date: Wed, 18 Dec 2002 15:19:17 -0800 [thread overview]
Message-ID: <20021218231917.GA1782@kroah.com> (raw)
Here are some minor cleanups for the existing LSM code, and a
capabilities patch from Bill Irwin.
Please pull from:
bk://lsm.bkbits.net/linus-2.5
thanks,
greg k-h
kernel/capability.c | 14 +++---
security/Kconfig | 7 ++-
security/dummy.c | 108 ---------------------------------------------------
security/root_plug.c | 3 +
security/security.c | 8 +++
5 files changed, 25 insertions(+), 115 deletions(-)
-----
ChangeSet@1.901, 2002-12-18 15:10:25-08:00, greg@kroah.com
LSM: update the copyright dates for my entry.
security/dummy.c | 2 +-
security/security.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
------
ChangeSet@1.900, 2002-12-18 15:09:33-08:00, greg@kroah.com
LSM: Fix up the description of the root_plug code to try to make it clearer.
security/Kconfig | 7 +++++--
security/root_plug.c | 3 +++
2 files changed, 8 insertions(+), 2 deletions(-)
------
ChangeSet@1.899, 2002-12-18 14:58:27-08:00, wli@holomorphy.com
[PATCH] converting cap_set_pg() to for_each_task_pid()
cap_set_pg() wants to find all processes in a given process group. This
converts it to use for_each_task_pid().
kernel/capability.c | 14 ++++++++------
1 files changed, 8 insertions(+), 6 deletions(-)
------
ChangeSet@1.898, 2002-12-18 14:57:38-08:00, greg@kroah.com
LSM: changed the dummy code to use the default operations logic.
security/dummy.c | 106 ----------------------------------------------------
security/security.c | 6 ++
2 files changed, 7 insertions(+), 105 deletions(-)
------
next reply other threads:[~2002-12-18 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 23:19 Greg KH [this message]
2002-12-18 23:21 ` Greg KH
2002-12-18 23:27 ` [PATCH] " Greg KH
2002-12-18 23:28 ` Greg KH
2002-12-18 23:29 ` Greg KH
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=20021218231917.GA1782@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=torvalds@transmeta.com \
/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
Powered by JetHome