From: penguin-kernel@I-love.SAKURA.ne.jp (Tetsuo Handa)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] LSM: Revive security_task_alloc() hook and per "struct task_struct" security blob.
Date: Sun, 26 Mar 2017 10:49:53 +0900 [thread overview]
Message-ID: <201703261049.FAI51524.OVFQtFSLHOFMOJ@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <1490355993-15773-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp>
James, would you teach me why this patch still cannot go to linux-next?
If we don't merge this patch now, we will again fail to land in 4.12.
> On 02/01/2017 08:02 PM, James Morris wrote:
> > On Wed, 1 Feb 2017, John Johansen wrote:
> >
> >> Sorry this took so long, it looks good to me, and I have done
> >> some builds and tests with apparmor using it. The apparmor patch
> >> to make use of this follows as a reply.
> >>
> >> Acked-by: John Johansen <john.johansen@canonical.com>
> >
> > We're too late in the -rc cycle to take these for 4.11. Please
> > keep testing them and some more review/acks would also be good.
> >
> Certainly, I didn't expect this to land in 4.11. I would really like
> get some feed back/review/ack from the owner of the task struct.
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-03-26 1:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 11:46 [PATCH] LSM: Revive security_task_alloc() hook and per "struct task_struct" security blob Tetsuo Handa
2017-03-24 12:11 ` José Bollo
2017-03-24 12:27 ` Tetsuo Handa
2017-03-26 1:49 ` Tetsuo Handa [this message]
2017-03-26 21:09 ` James Morris
2017-03-28 0:21 ` James Morris
2017-03-28 11:02 ` Tetsuo Handa
-- strict thread matches above, loose matches on Subject: below --
2017-03-12 4:35 Tetsuo Handa
2017-03-13 15:37 ` Serge E. Hallyn
2017-03-16 11:09 ` Tetsuo Handa
2017-03-13 16:08 ` Casey Schaufler
2017-03-17 10:37 ` Tetsuo Handa
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=201703261049.FAI51524.OVFQtFSLHOFMOJ@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=linux-security-module@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.