From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: linux-integrity <linux-integrity@vger.kernel.org>
Cc: Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Subject: Re: ima: temporary "next-queued-testing" branch (UPDATE)
Date: Mon, 11 Dec 2017 17:02:06 -0500 [thread overview]
Message-ID: <1513029726.3530.29.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <1512564458.4698.33.camel@linux.vnet.ibm.com>
On Wed, 2017-12-06 at 07:47 -0500, Mimi Zohar wrote:
> Hi -
>
> Before upstreaming "ima: re-introduce own integrity cache lock", I've
> pushed the following patches to the next-queued-testing branch for
> testing. We'll resync with the linux-security tree based on -rc3,
> hopefully next week.
>
> d79d361c25d7 ima: re-introduce own integrity cache lock
> 4e94bcf160f2 ima: support new "hash" and "dont_hash" policy actions
> bd1fa1e14733 ima: Fix line continuation format
> cf46932b9a02 ima: pass filename to ima_rdwr_violation_check()
> 4aad0b3845e4 ima: log message to module appraisal error
We're now sync'ed with the security tree next-general branch. There
are a few differences, nothing major, between the "next-queued-
testing" branch and the "next-integrity" branch.
For those posting IMA/EVM patches, please base them on the
git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity
branch.
Sorry for any inconveniences this might have caused.
thanks,
Mimi
next prev parent reply other threads:[~2017-12-11 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 12:47 ima: temporary "next-queued-testing" branch Mimi Zohar
2017-12-11 22:02 ` Mimi Zohar [this message]
2017-12-18 15:30 ` ima: temporary "next-queued-testing" branch (UPDATE) Mimi Zohar
2017-12-18 20:43 ` Stephen Rothwell
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=1513029726.3530.29.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=linux-integrity@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).