From: zohar@linux.vnet.ibm.com (Mimi Zohar)
To: linux-security-module@vger.kernel.org
Subject: Kernel repository updated to v4.11-rc1 *** reverted ??? ***
Date: Mon, 13 Mar 2017 08:04:09 -0400 [thread overview]
Message-ID: <1489406649.28954.143.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1703061115270.31922@namei.org>
On Mon, 2017-03-06 at 11:18 +1100, James Morris wrote:
> FYI, I've merged security-next with v4.11-rc1 and then merged the
> following queued patches:
>
> ca97d939db114c8d1619e10a3b82af8615372dae security: mark LSM hooks as __ro_after_init
> dd0859dccbe291cf8179a96390f5c0e45cb9af1d security: introduce CONFIG_SECURITY_WRITABLE_HOOKS
> 84e6885e9e6a818d1ca1eabb9b720b357ab07a8b selinux: fix kernel BUG on prlimit(..., NULL, NULL)
> 791ec491c372f49cea3ea7a7143454a9023ac9d4 prlimit,security,selinux: add a security hook for prlimit
>
> Please test!
The current tip of the linux-security #next branch has been reverted to
commit 61841be6358c "tpm: declare tpm2_get_pcr_allocation() as static".
Was this intentional?
I'm seeing ...
$ git status
On branch security-next
Your branch is ahead of 'security/next' by 13176 commits.
(use "git push" to publish your local commits)
Untracked files:
(use "git add <file>..." to include in what will be committed)
ca-cert.pem
ca-cert.x509
nothing added to commit but untracked files present (use "git add" to
track)]
$ git log --oneline -5
ca97d939db11 security: mark LSM hooks as __ro_after_init
dd0859dccbe2 security: introduce CONFIG_SECURITY_WRITABLE_HOOKS
84e6885e9e6a selinux: fix kernel BUG on prlimit(..., NULL, NULL)
791ec491c372 prlimit,security,selinux: add a security hook for prlimit
c1ae3cfa0e89 Linux 4.11-rc1
Mimi
--
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-13 12:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LRH.2.20.1703061115270.31922@namei.org>
2017-03-06 17:19 ` Fwd: Kernel repository updated to v4.11-rc1 Paul Moore
[not found] ` <1488823937.674.13.camel@tycho.nsa.gov>
2017-03-08 6:04 ` James Morris
2017-03-13 12:04 ` Mimi Zohar [this message]
2017-03-13 14:40 ` Kernel repository updated to v4.11-rc1 *** reverted ??? *** James Morris
2017-03-13 14:53 ` Konstantin Ryabitsev
2017-03-13 15:07 ` Mimi Zohar
2017-03-13 15:33 ` Konstantin Ryabitsev
2017-03-13 15:40 ` Mimi Zohar
2017-03-13 16:05 ` Konstantin Ryabitsev
2017-03-13 16:10 ` Mimi Zohar
2017-03-13 22:03 ` James Morris
2017-03-13 22:00 ` James Morris
2017-03-13 22:01 ` James Morris
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=1489406649.28954.143.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--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.