* linux-integrity
@ 2014-06-06 3:55 Mimi Zohar
2014-06-06 4:22 ` linux-integrity Stephen Rothwell
0 siblings, 1 reply; 7+ messages in thread
From: Mimi Zohar @ 2014-06-06 3:55 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next
Hi Stephan,
Please include
git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity
#next in linux-next.
thanks,
Mimi
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: linux-integrity
2014-06-06 3:55 linux-integrity Mimi Zohar
@ 2014-06-06 4:22 ` Stephen Rothwell
2014-06-06 5:11 ` linux-integrity Mimi Zohar
0 siblings, 1 reply; 7+ messages in thread
From: Stephen Rothwell @ 2014-06-06 4:22 UTC (permalink / raw)
To: Mimi Zohar; +Cc: linux-next
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
Hi Mimi,
On Thu, 05 Jun 2014 23:55:56 -0400 Mimi Zohar <zohar@linux•vnet.ibm.com> wrote:
>
> Please include
> git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity
> #next in linux-next.
OK, it would be good to know what that tree is about ... also it is
really late for inclusion in v3.16 even - I generally do not add trees
to linux-next during the merge window. This does not mean I won't
include it if you can convince me otherwise ...
Also, you should cc this request to people/mailing lists that may have
a stake or interest in what the tree contains and consider these things
about inclusion:
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgment of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: linux-integrity
2014-06-06 4:22 ` linux-integrity Stephen Rothwell
@ 2014-06-06 5:11 ` Mimi Zohar
2014-06-06 7:21 ` linux-integrity Stephen Rothwell
2014-06-06 7:56 ` linux-integrity Stephen Rothwell
0 siblings, 2 replies; 7+ messages in thread
From: Mimi Zohar @ 2014-06-06 5:11 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-security-module
On Fri, 2014-06-06 at 14:22 +1000, Stephen Rothwell wrote:
> Hi Mimi,
>
> On Thu, 05 Jun 2014 23:55:56 -0400 Mimi Zohar <zohar@linux•vnet.ibm.com> wrote:
> >
> > Please include
> > git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity
> > #next in linux-next.
>
> OK, it would be good to know what that tree is about
The linux-integrity measures, appraises and enforces local file
integrity, and audit logs file hashes based on policy. The
linux-integrity subsystem is upstreamed and pulled into linux-next via
linux-security. A suggestion was made to have the linux-integrity
subsystem pulled directly into linux-next.
> ... also it is
> really late for inclusion in v3.16 even - I generally do not add trees
> to linux-next during the merge window. This does not mean I won't
> include it if you can convince me otherwise ...
8 patches, mostly bugs fixes, are queued to be upstreamed
http://marc.info/?l=linux-security-module&m=140128032831578&w=2
Please add the linux-integrity subsystem at the next feasible
opportunity.
thanks,
Mimi
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: linux-integrity
2014-06-06 5:11 ` linux-integrity Mimi Zohar
@ 2014-06-06 7:21 ` Stephen Rothwell
2014-06-06 7:56 ` linux-integrity Stephen Rothwell
1 sibling, 0 replies; 7+ messages in thread
From: Stephen Rothwell @ 2014-06-06 7:21 UTC (permalink / raw)
To: Mimi Zohar; +Cc: linux-next, linux-security-module
[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]
Hi Mimi,
On Fri, 06 Jun 2014 01:11:09 -0400 Mimi Zohar <zohar@linux•vnet.ibm.com> wrote:
>
> On Fri, 2014-06-06 at 14:22 +1000, Stephen Rothwell wrote:
> >
> > On Thu, 05 Jun 2014 23:55:56 -0400 Mimi Zohar <zohar@linux•vnet.ibm.com> wrote:
> > >
> > > Please include
> > > git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity
> > > #next in linux-next.
> >
> > OK, it would be good to know what that tree is about
>
> The linux-integrity measures, appraises and enforces local file
> integrity, and audit logs file hashes based on policy. The
> linux-integrity subsystem is upstreamed and pulled into linux-next via
> linux-security. A suggestion was made to have the linux-integrity
> subsystem pulled directly into linux-next.
>
> > ... also it is
> > really late for inclusion in v3.16 even - I generally do not add trees
> > to linux-next during the merge window. This does not mean I won't
> > include it if you can convince me otherwise ...
>
> 8 patches, mostly bugs fixes, are queued to be upstreamed
> http://marc.info/?l=linux-security-module&m=140128032831578&w=2
> Please add the linux-integrity subsystem at the next feasible
> opportunity.
I was unaware of the other discussion, so no worries - I will add your
tree from Tuesday (as Monday is a Public Holiday here). I hope that
will help.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: linux-integrity
2014-06-06 5:11 ` linux-integrity Mimi Zohar
2014-06-06 7:21 ` linux-integrity Stephen Rothwell
@ 2014-06-06 7:56 ` Stephen Rothwell
2014-06-06 11:43 ` linux-integrity Mimi Zohar
1 sibling, 1 reply; 7+ messages in thread
From: Stephen Rothwell @ 2014-06-06 7:56 UTC (permalink / raw)
To: Mimi Zohar; +Cc: linux-next, linux-security-module
[-- Attachment #1: Type: text/plain, Size: 2226 bytes --]
Hi Mimi,
On Fri, 06 Jun 2014 01:11:09 -0400 Mimi Zohar <zohar@linux•vnet.ibm.com> wrote:
>
> On Fri, 2014-06-06 at 14:22 +1000, Stephen Rothwell wrote:
> >
> > On Thu, 05 Jun 2014 23:55:56 -0400 Mimi Zohar <zohar@linux•vnet.ibm.com> wrote:
> > >
> > > Please include
> > > git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity
> > > #next in linux-next.
> >
> > OK, it would be good to know what that tree is about
>
> The linux-integrity measures, appraises and enforces local file
> integrity, and audit logs file hashes based on policy. The
> linux-integrity subsystem is upstreamed and pulled into linux-next via
> linux-security. A suggestion was made to have the linux-integrity
> subsystem pulled directly into linux-next.
>
> > ... also it is
> > really late for inclusion in v3.16 even - I generally do not add trees
> > to linux-next during the merge window. This does not mean I won't
> > include it if you can convince me otherwise ...
>
> 8 patches, mostly bugs fixes, are queued to be upstreamed
> http://marc.info/?l=linux-security-module&m=140128032831578&w=2
> Please add the linux-integrity subsystem at the next feasible
> opportunity.
Added from Tuesday. I have just you listed as the contact in case of
problems with the tree - let me know if anyone else should also be
informed.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgment of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: linux-integrity
2014-06-06 7:56 ` linux-integrity Stephen Rothwell
@ 2014-06-06 11:43 ` Mimi Zohar
2014-06-06 14:20 ` linux-integrity Stephen Rothwell
0 siblings, 1 reply; 7+ messages in thread
From: Mimi Zohar @ 2014-06-06 11:43 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-security-module, Dmitry Kasatkin
On Fri, 2014-06-06 at 17:56 +1000, Stephen Rothwell wrote:
> Hi Mimi,
>
> On Fri, 06 Jun 2014 01:11:09 -0400 Mimi Zohar <zohar@linux•vnet.ibm.com> wrote:
> >
> > On Fri, 2014-06-06 at 14:22 +1000, Stephen Rothwell wrote:
> > >
> > > On Thu, 05 Jun 2014 23:55:56 -0400 Mimi Zohar <zohar@linux•vnet.ibm.com> wrote:
> > > >
> > > > Please include
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity
> > > > #next in linux-next.
> > >
> > > OK, it would be good to know what that tree is about
> >
> > The linux-integrity measures, appraises and enforces local file
> > integrity, and audit logs file hashes based on policy. The
> > linux-integrity subsystem is upstreamed and pulled into linux-next via
> > linux-security. A suggestion was made to have the linux-integrity
> > subsystem pulled directly into linux-next.
> >
> > > ... also it is
> > > really late for inclusion in v3.16 even - I generally do not add trees
> > > to linux-next during the merge window. This does not mean I won't
> > > include it if you can convince me otherwise ...
> >
> > 8 patches, mostly bugs fixes, are queued to be upstreamed
> > http://marc.info/?l=linux-security-module&m=140128032831578&w=2
> > Please add the linux-integrity subsystem at the next feasible
> > opportunity.
>
> Added from Tuesday. I have just you listed as the contact in case of
> problems with the tree - let me know if anyone else should also be
> informed.
Thanks! Yes, please add Dmitry Kasatkin (cc'ed).
Mimi
> Thanks for adding your subsystem tree as a participant of linux-next. As
> you may know, this is not a judgment of your code. The purpose of
> linux-next is for integration testing and to lower the impact of
> conflicts between subsystems in the next merge window.
>
> You will need to ensure that the patches/commits in your tree/series have
> been:
> * submitted under GPL v2 (or later) and include the Contributor's
> Signed-off-by,
> * posted to the relevant mailing list,
> * reviewed by you (or another maintainer of your subsystem tree),
> * successfully unit tested, and
> * destined for the current or next Linux merge window.
>
> Basically, this should be just what you would send to Linus (or ask him
> to fetch). It is allowed to be rebased if you deem it necessary.
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: linux-integrity
2014-06-06 11:43 ` linux-integrity Mimi Zohar
@ 2014-06-06 14:20 ` Stephen Rothwell
0 siblings, 0 replies; 7+ messages in thread
From: Stephen Rothwell @ 2014-06-06 14:20 UTC (permalink / raw)
To: Mimi Zohar; +Cc: linux-next, linux-security-module, Dmitry Kasatkin
[-- Attachment #1: Type: text/plain, Size: 232 bytes --]
Hi Mimi,
On Fri, 06 Jun 2014 07:43:41 -0400 Mimi Zohar <zohar@linux•vnet.ibm.com> wrote:
>
> Thanks! Yes, please add Dmitry Kasatkin (cc'ed).
Done.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2014-06-06 14:20 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-06-06 3:55 linux-integrity Mimi Zohar
2014-06-06 4:22 ` linux-integrity Stephen Rothwell
2014-06-06 5:11 ` linux-integrity Mimi Zohar
2014-06-06 7:21 ` linux-integrity Stephen Rothwell
2014-06-06 7:56 ` linux-integrity Stephen Rothwell
2014-06-06 11:43 ` linux-integrity Mimi Zohar
2014-06-06 14:20 ` linux-integrity Stephen Rothwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox