* ima: temporary "next-queued-testing" branch
@ 2017-12-06 12:47 Mimi Zohar
2017-12-11 22:02 ` ima: temporary "next-queued-testing" branch (UPDATE) Mimi Zohar
0 siblings, 1 reply; 6+ messages in thread
From: Mimi Zohar @ 2017-12-06 12:47 UTC (permalink / raw)
To: linux-integrity
Cc: Dmitry Kasatkin, Bruno E. O. Meneguele, Joe Perches,
Roberto Sassu, James Morris
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
thanks,
Mimi
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ima: temporary "next-queued-testing" branch (UPDATE)
2017-12-06 12:47 ima: temporary "next-queued-testing" branch Mimi Zohar
@ 2017-12-11 22:02 ` Mimi Zohar
2017-12-18 15:30 ` Mimi Zohar
0 siblings, 1 reply; 6+ messages in thread
From: Mimi Zohar @ 2017-12-11 22:02 UTC (permalink / raw)
To: linux-integrity; +Cc: Dmitry Kasatkin
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ima: temporary "next-queued-testing" branch (UPDATE)
2017-12-11 22:02 ` ima: temporary "next-queued-testing" branch (UPDATE) Mimi Zohar
@ 2017-12-18 15:30 ` Mimi Zohar
0 siblings, 0 replies; 6+ messages in thread
From: Mimi Zohar @ 2017-12-18 15:30 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-integrity, Jeff Layton, James Morris
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://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.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?
thanks!
Mimi
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ima: temporary "next-queued-testing" branch (UPDATE)
@ 2017-12-18 15:30 ` Mimi Zohar
0 siblings, 0 replies; 6+ messages in thread
From: Mimi Zohar @ 2017-12-18 15:30 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-integrity, Jeff Layton, James Morris
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://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.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?
thanks!
Mimi
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ima: temporary "next-queued-testing" branch (UPDATE)
2017-12-18 15:30 ` Mimi Zohar
@ 2017-12-18 20:43 ` Stephen Rothwell
-1 siblings, 0 replies; 6+ messages in thread
From: Stephen Rothwell @ 2017-12-18 20:43 UTC (permalink / raw)
To: Mimi Zohar; +Cc: linux-next, linux-integrity, Jeff Layton, James Morris
Hi Mimi,
On Mon, 18 Dec 2017 10:30:47 -0500 Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
>
> 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?
Done.
--
Cheers,
Stephen Rothwell
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ima: temporary "next-queued-testing" branch (UPDATE)
@ 2017-12-18 20:43 ` Stephen Rothwell
0 siblings, 0 replies; 6+ messages in thread
From: Stephen Rothwell @ 2017-12-18 20:43 UTC (permalink / raw)
To: Mimi Zohar; +Cc: linux-next, linux-integrity, Jeff Layton, James Morris
Hi Mimi,
On Mon, 18 Dec 2017 10:30:47 -0500 Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
>
> 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?
Done.
--
Cheers,
Stephen Rothwell
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-12-18 20:43 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-12-06 12:47 ima: temporary "next-queued-testing" branch Mimi Zohar
2017-12-11 22:02 ` ima: temporary "next-queued-testing" branch (UPDATE) Mimi Zohar
2017-12-18 15:30 ` Mimi Zohar
2017-12-18 15:30 ` Mimi Zohar
2017-12-18 20:43 ` Stephen Rothwell
2017-12-18 20:43 ` Stephen Rothwell
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.