From: James Morris <jmorris@namei.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH v3] tomoyo: Swicth from cred->security to task_struct->security.
Date: Thu, 24 Jan 2019 06:34:59 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1901240634380.28095@namei.org> (raw)
In-Reply-To: <765b2ad7-a6a6-617a-5270-c41b1fe43ad4@I-love.SAKURA.ne.jp>
On Wed, 23 Jan 2019, Tetsuo Handa wrote:
> Hello.
>
> This is effectively a pull request, for I don't maintain a git tree.
> If no questions, please apply to linux-security.git#next-general.
Patches are perfectly fine, just include me in the To: line and say that
you want it applied.
>
> On 2019/01/19 23:11, Tetsuo Handa wrote:
> > TOMOYO security module is designed to use "struct task_struct"->security
> > in order to allow per "struct task_struct" tracking without being disturbed
> > by unable to update "struct cred"->security due to override mechanism.
> >
> > Now that infrastructure-managed security blob is ready, this patch updates
> > TOMOYO to use "struct task_struct"->security.
> >
> > Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> > ---
> > security/tomoyo/common.c | 4 +-
> > security/tomoyo/common.h | 45 ++++--------
> > security/tomoyo/domain.c | 11 +--
> > security/tomoyo/securityfs_if.c | 21 ++----
> > security/tomoyo/tomoyo.c | 149 +++++++++++++++++++++-------------------
> > 5 files changed, 108 insertions(+), 122 deletions(-)
>
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2019-01-23 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 10:18 [PATCH] tomoyo: Swicth from cred->security to task_struct->security Tetsuo Handa
2019-01-18 14:49 ` [PATCH v2] " Tetsuo Handa
2019-01-19 14:11 ` [PATCH v3] " Tetsuo Handa
2019-01-23 9:49 ` Tetsuo Handa
2019-01-23 19:34 ` James Morris [this message]
2019-01-23 19:38 ` James Morris
2019-01-18 17:01 ` [PATCH] " Casey Schaufler
2019-01-18 17:17 ` Tetsuo Handa
2019-01-18 18:02 ` 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.21.1901240634380.28095@namei.org \
--to=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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