archive mirror
 help / color / mirror / Atom feed
From: Mimi Zohar <>
To: Stephen Rothwell <>
Cc: linux-next <>,
	linux-integrity <>,
	Jeff Layton <>,
	James Morris <>
Subject: Re: ima:  temporary "next-queued-testing" branch  (UPDATE)
Date: Mon, 18 Dec 2017 10:30:47 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Stephen,

On Mon, 2017-12-11 at 17:02 -0500, Mimi Zohar wrote:
> 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:// next-integrity
> branch.
> Sorry for any inconveniences this might have caused.

As the integrity subsystem is now back in sync with the security tree,
 I'd really appreciate if you could include the integrity tree in
linux-next.  Instead of including the integrity "next" branch as
previously, could you include the "next-integrity" branch instead?



       reply	other threads:[~2017-12-18 15:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2017-12-18 15:30   ` Mimi Zohar [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: ima:  temporary "next-queued-testing" branch  (UPDATE)' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).