From: konstantin@linuxfoundation.org (Konstantin Ryabitsev)
To: linux-security-module@vger.kernel.org
Subject: Kernel repository updated to v4.11-rc1 *** reverted ??? ***
Date: Mon, 13 Mar 2017 10:53:18 -0400 [thread overview]
Message-ID: <20170313145318.GA20608@gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1703140123580.23070@namei.org>
On Tue, Mar 14, 2017 at 01:40:14AM +1100, James Morris wrote:
>On Mon, 13 Mar 2017, Mimi Zohar wrote:
>
>> 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?
>>
>
>That's very odd. It looks correct via git web:
>https://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git/log/?h=next
>
>(ca97d939)
>
>but when I clone a new tree, I see what you see (61841be6358c).
>
>Did you see a forced update message when you pulled?
>
>Perhaps there was a disk restore at kernel.org?
Can you tell me precise origin paths for where things are correct and
where things are wrong?
-K
--
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 14:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LRH.2.20.1703061115270.31922@namei.org>
[not found] ` <1488823937.674.13.camel@tycho.nsa.gov>
2017-03-08 6:04 ` Kernel repository updated to v4.11-rc1 James Morris
2017-03-13 12:04 ` Kernel repository updated to v4.11-rc1 *** reverted ??? *** Mimi Zohar
2017-03-13 14:40 ` James Morris
2017-03-13 14:53 ` Konstantin Ryabitsev [this message]
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=20170313145318.GA20608@gmail.com \
--to=konstantin@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).