Skip to contentSkip to conversation

Change in security maintainer for a few weeks

DISCUSSION Greg KH 11 participants 20 messages Jun 5, 2014 – Jun 11, 2014

lore
Share & tools
lore

Greg KH

author
#0 lore raw

Hi all,

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

I'll take his git tree on kernel.org and push those to Linus for 3.16-rc1, as those look like they have had proper testing in linux-next.

But there only seems to be 14 patches in there. Are there pending patches that people have been sending and need to get in besides those?

thanks,

greg k-h

#1 lore raw
Quoted 11 lines · Greg KH

Hi all,

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

I'll take his git tree on kernel.org and push those to Linus for 3.16-rc1, as those look like they have had proper testing in linux-next.

But there only seems to be 14 patches in there. Are there pending patches that people have been sending and need to get in besides those?

Serge seems to have already done this?

https://lkml.org/lkml/2014/6/4/350

Confused...

josh

#2 lore raw
Quoted 10 lines · Josh Boyer
Quoted 9 lines · Greg KH

Hi all,

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

I'll take his git tree on kernel.org and push those to Linus for 3.16-rc1, as those look like they have had proper testing in linux-next.

Quoted 8 lines
Quoted 2 lines

But there only seems to be 14 patches in there. Are there pending patches that people have been sending and need to get in besides those?

Serge seems to have already done this?

https://lkml.org/lkml/2014/6/4/350

Confused...

Yes, but (this time :) James didn't actually ask me to, so if he asked Greg that's great. Greg, the 5 patches I added on top of James' tree were 4 from Paul which are already in linux-next, and one (the highest priority one out of a larger set) from Mimi. If you could add those that would be great.

thanks,
-serge

author
#3 lore raw
In reply to Josh Boyer
Quoted 10 lines · Josh Boyer
Quoted 9 lines · Greg KH

Hi all,

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

I'll take his git tree on kernel.org and push those to Linus for 3.16-rc1, as those look like they have had proper testing in linux-next.

Quoted 6 lines
Quoted 2 lines

But there only seems to be 14 patches in there. Are there pending patches that people have been sending and need to get in besides those?

Serge seems to have already done this?

https://lkml.org/lkml/2014/6/4/350

Ah, that's good, but wasn't sent to the linux-security-module list where I would have noticed it :(

The patches also don't seem to have ended up in Linus's tree either yet...

Serge, are you going to be doing this in replacement of James for a while? What made you push these to Linus and not tell the security list?

Quoted 1 line

Confused...

Me as well...

greg k-h

#4 lore raw
Quoted 18 lines · Greg KH
Quoted 10 lines · Josh Boyer
Quoted 9 lines · Greg KH

Hi all,

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

I'll take his git tree on kernel.org and push those to Linus for 3.16-rc1, as those look like they have had proper testing in linux-next.

Quoted 6 lines
Quoted 2 lines

But there only seems to be 14 patches in there. Are there pending patches that people have been sending and need to get in besides those?

Serge seems to have already done this?

https://lkml.org/lkml/2014/6/4/350

Quoted 8 lines

Ah, that's good, but wasn't sent to the linux-security-module list where I would have noticed it :(

The patches also don't seem to have ended up in Linus's tree either yet...

Serge, are you going to be doing this in replacement of James for a while?

I don't mind, but I definately don't mind if you do. In the past with planned vacations James has asked me to babysit the tree, so I just wanted to make sure it didn't get neglected. But he did not ask me, I'm just an interloper.

Quoted 2 lines

What made you push these to Linus and not tell the security
list?

Abject failure on my part, sorry.

Quoted 10 lines
Quoted 1 line

Confused...

Me as well...

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

author
#5 lore raw
Quoted 25 lines · Serge E. Hallyn
Quoted 24 lines · Greg KH
Quoted 10 lines · Josh Boyer
Quoted 9 lines · Greg KH

Hi all,

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

I'll take his git tree on kernel.org and push those to Linus for 3.16-rc1, as those look like they have had proper testing in linux-next.

Quoted 6 lines
Quoted 2 lines

But there only seems to be 14 patches in there. Are there pending patches that people have been sending and need to get in besides those?

Serge seems to have already done this?

https://lkml.org/lkml/2014/6/4/350

Ah, that's good, but wasn't sent to the linux-security-module list where I would have noticed it :(

The patches also don't seem to have ended up in Linus's tree either yet...

Quoted 7 lines
Quoted 2 lines

Serge, are you going to be doing this in replacement of James for a while?

I don't mind, but I definately don't mind if you do. In the past with planned vacations James has asked me to babysit the tree, so I just wanted to make sure it didn't get neglected. But he did not ask me, I'm just an interloper.

That's great, I wasn't aware of this. Feel free to keep doing this and taking over for now. As you already have a kernel.org account, and have done it in the past, it only makes sense for you to continue.

But next time, cc: the subsystem mailing list :)

thanks,

greg k-h

#6 lore raw
In reply to Greg KH
Quoted 6 lines · Greg KH

Hi all,

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

Quoted 8 lines

I'll take his git tree on kernel.org and push those to Linus for 3.16-rc1, as those look like they have had proper testing in linux-next.

But there only seems to be 14 patches in there. Are there pending patches that people have been sending and need to get in besides those?

thanks,

Hi Greg,

Mimi sent pull request to James last week without any response...

But that is based on James' 3.14 tree..
May be Mimi need to rebase and send pull request to you..

Thanks,

- Dmitry

Quoted 5 lines

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 2 lines
Thanks,
Dmitry
#7 lore raw
Quoted 16 lines · Dmitry Kasatkin
Quoted 6 lines · Greg KH

Hi all,

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

Quoted 8 lines

I'll take his git tree on kernel.org and push those to Linus for 3.16-rc1, as those look like they have had proper testing in linux-next.

But there only seems to be 14 patches in there. Are there pending patches that people have been sending and need to get in besides those?

thanks,

Quoted 6 lines

Hi Greg,

Mimi sent pull request to James last week without any response...

But that is based on James' 3.14 tree..
May be Mimi need to rebase and send pull request to you..

I'm really sorry Dmitry. Unlike the SELinux patches, the integrity patches didn't make it into linux-next. Based on Paul's suggestion, I'll request that the linux-integrity tree be added to the list of trees that are pulled directly into linux-next, instead of waiting for it to go in via the security tree.

Mimi

#8 lore raw
In reply to Greg KH
Quoted 11 lines · Greg KH

Hi all,

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

I'll take his git tree on kernel.org and push those to Linus for 3.16-rc1, as those look like they have had proper testing in linux-next.

But there only seems to be 14 patches in there. Are there pending patches that people have been sending and need to get in besides those?

I have two patches.

http://marc.info/?l=linux-security-module&m=140122694916418&w=4
I got an ACK from each subsystem maintainer and expected it to go to 3.15-final, but seems that it can't even go to 3.16-final for unknown reason because James is not responding. Maybe James wants this patch reviewed by more people, but it seems to me that linux-security-module ML itself is not working.

http://marc.info/?l=linux-security-module&m=140180521023726&w=4
It got reviewed by Paul and Serge, but seems that it can't go to 3.16-final for unknown reason.

#9 lore raw
In reply to Greg KH
Quoted 3 lines · Greg KH

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

As exactly this (working with active contributors to help co-maintain the subsystem) has been brought at the ksummit maling list, I am just curious whether noone else actively working in that area was willing to step up?

	$ ./scripts/get_maintainer.pl --git -f security/
	James Morris <[email protected]> (supporter:SECURITY SUBSYSTEM)
	Mimi Zohar <[email protected]> (commit_signer:51/220=23%)
	Paul Moore <[email protected]> (commit_signer:43/220=20%,authored:24/220=11%)
	Eric Paris <[email protected]> (commit_signer:43/220=20%,authored:16/220=7%)
	David Howells <[email protected]> (commit_signer:29/220=13%,authored:24/220=11%)
	Roberto Sassu <[email protected]> (commit_signer:24/220=11%,authored:19/220=9%)
	John Johansen <[email protected]> (authored:20/220=9%)

If not, then I think this can be shown as a prime example why the problem of "non-substituability" of many maintainers is actually real.

Thanks,

Signature · 2 lines
Jiri Kosina
SUSE Labs
#10 lore raw
Quoted 9 lines · Jiri Kosina
Quoted 3 lines · Greg KH

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

As exactly this (working with active contributors to help co-maintain the subsystem) has been brought at the ksummit maling list, I am just curious whether noone else actively working in that area was willing to step up?

Quoted 6 lines
	$ ./scripts/get_maintainer.pl --git -f security/
	James Morris <[email protected]> (supporter:SECURITY SUBSYSTEM)
   ...

If not, then I think this can be shown as a prime example why the problem of "non-substituability" of many maintainers is actually real.

Once several of us became aware that James was stepping away for a few weeks (I should mention this was not a planned absence and took most of us by surprise) we had a brief discussion off-list and several of us did offer to "step-up"; Serge had already created a repo and since he had pushed patches while James was away in the past it seemed a reasonable approach this time around.

Signature · 2 lines
paul moore
www.paul-moore.com
author
#11 lore raw
Quoted 17 lines · Paul Moore
Quoted 9 lines · Jiri Kosina
Quoted 3 lines · Greg KH

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

As exactly this (working with active contributors to help co-maintain the subsystem) has been brought at the ksummit maling list, I am just curious whether noone else actively working in that area was willing to step up?

Quoted 6 lines
	$ ./scripts/get_maintainer.pl --git -f security/
	James Morris <[email protected]> (supporter:SECURITY SUBSYSTEM)
   ...

If not, then I think this can be shown as a prime example why the problem of "non-substituability" of many maintainers is actually real.

Quoted 6 lines

Once several of us became aware that James was stepping away for a few weeks (I should mention this was not a planned absence and took most of us by surprise) we had a brief discussion off-list and several of us did offer to "step-up"; Serge had already created a repo and since he had pushed patches while James was away in the past it seemed a reasonable approach this time around.

That's great, as the communication around this has not been very much (an non-existant on the subsystem mailing list) I was not aware of it.

If Serge wants to do this, and as he has been the stand-in for James in the past, I have _no_ objection to this at all.

Serge, feel free to resend your patches to Linus if he doesn't pick them up in a few days, with the information that you are doing this in James's absence for a while.

So, that was easy, I don't have to do this at all, great.

greg k-h

#12 lore raw
Quoted 28 lines · Greg KH
Quoted 17 lines · Paul Moore
Quoted 9 lines · Jiri Kosina
Quoted 3 lines · Greg KH

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

As exactly this (working with active contributors to help co-maintain the subsystem) has been brought at the ksummit maling list, I am just curious whether noone else actively working in that area was willing to step up?

Quoted 6 lines
	$ ./scripts/get_maintainer.pl --git -f security/
	James Morris <[email protected]> (supporter:SECURITY SUBSYSTEM)
   ...

If not, then I think this can be shown as a prime example why the problem of "non-substituability" of many maintainers is actually real.

Quoted 6 lines

Once several of us became aware that James was stepping away for a few weeks (I should mention this was not a planned absence and took most of us by surprise) we had a brief discussion off-list and several of us did offer to "step-up"; Serge had already created a repo and since he had pushed patches while James was away in the past it seemed a reasonable approach this time around.

That's great, as the communication around this has not been very much (an non-existant on the subsystem mailing list) I was not aware of it.

Quoted 6 lines

If Serge wants to do this, and as he has been the stand-in for James in the past, I have _no_ objection to this at all.

Serge, feel free to resend your patches to Linus if he doesn't pick them up in a few days, with the information that you are doing this in James's absence for a while.

Will do (and wil cc: lsm).

Quoted 3 lines

So, that was easy, I don't have to do this at all, great.

greg k-h

#13 lore raw
Quoted 26 lines · Serge Hallyn
Quoted 25 lines · Greg KH
Quoted 13 lines · Paul Moore
Quoted 12 lines · Jiri Kosina
Quoted 3 lines · Greg KH

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

As exactly this (working with active contributors to help co-maintain the subsystem) has been brought at the ksummit maling list, I am just curious whether noone else actively working in that area was willing to step up?

	$ ./scripts/get_maintainer.pl --git -f security/
	James Morris <[email protected]> (supporter:SECURITY SUBSYSTEM)
   ...
Quoted 8 lines
Quoted 2 lines

If not, then I think this can be shown as a prime example why the problem of "non-substituability" of many maintainers is actually real.

Once several of us became aware that James was stepping away for a few weeks (I should mention this was not a planned absence and took most of us by surprise) we had a brief discussion off-list and several of us did offer to "step-up"; Serge had already created a repo and since he had pushed patches while James was away in the past it seemed a reasonable approach this time around.

That's great, as the communication around this has not been very much (an non-existant on the subsystem mailing list) I was not aware of it.

Quoted 11 lines
Quoted 6 lines

If Serge wants to do this, and as he has been the stand-in for James in the past, I have _no_ objection to this at all.

Serge, feel free to resend your patches to Linus if he doesn't pick them up in a few days, with the information that you are doing this in James's absence for a while.

Will do (and wil cc: lsm).

Quoted 3 lines

So, that was easy, I don't have to do this at all, great.

greg k-h

How can I verify that the pull James accepted from me is moving forward somehow? Or, if it isn't, where does it go now?

Quoted 9 lines · Casey Schaufler

The following changes since commit f64410ec665479d7b4b77b7519e814253ed0f686:

selinux: correctly label /proc inodes in use before the policy is loaded (2014-03-19 16:46:18 -0400)

are available in the git repository at:

git://git.gitorious.org/smack-next/kernel.git smack-for-3.16

for you to fetch changes up to ec554fa75ec94dcf47e52db9551755679c10235b:

Thanks, pulled.

-- James Morris <[email protected]>

Quoted 5 lines

--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#14 lore raw
Quoted 33 lines · Casey Schaufler
Quoted 32 lines · Serge Hallyn
Quoted 31 lines · Greg KH
Quoted 13 lines · Paul Moore
Quoted 12 lines · Jiri Kosina
Quoted 3 lines · Greg KH

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

As exactly this (working with active contributors to help co-maintain the subsystem) has been brought at the ksummit maling list, I am just curious whether noone else actively working in that area was willing to step up?

	$ ./scripts/get_maintainer.pl --git -f security/
	James Morris <[email protected]> (supporter:SECURITY SUBSYSTEM)
   ...
Quoted 8 lines
Quoted 2 lines

If not, then I think this can be shown as a prime example why the problem of "non-substituability" of many maintainers is actually real.

Once several of us became aware that James was stepping away for a few weeks (I should mention this was not a planned absence and took most of us by surprise) we had a brief discussion off-list and several of us did offer to "step-up"; Serge had already created a repo and since he had pushed patches while James was away in the past it seemed a reasonable approach this time around.

That's great, as the communication around this has not been very much (an non-existant on the subsystem mailing list) I was not aware of it.

If Serge wants to do this, and as he has been the stand-in for James in the past, I have _no_ objection to this at all.

Serge, feel free to resend your patches to Linus if he doesn't pick them up in a few days, with the information that you are doing this in James's absence for a while.

Quoted 8 lines
Quoted 5 lines

Will do (and wil cc: lsm).

Quoted 3 lines

So, that was easy, I don't have to do this at all, great.

greg k-h

How can I verify that the pull James accepted from me is moving forward somehow? Or, if it isn't, where does it go now?

You can see it at
https://git.kernel.org/cgit/linux/kernel/git/sergeh/linux-security.git/log/security/smack?h=serge-next-1
As Greg suggested if Linus doesn't pull it in a few days I will resend the pull request.

#15 lore raw
Quoted 38 lines · Serge E. Hallyn
Quoted 37 lines · Casey Schaufler
Quoted 36 lines · Serge Hallyn
Quoted 25 lines · Greg KH
Quoted 13 lines · Paul Moore
Quoted 12 lines · Jiri Kosina
Quoted 3 lines · Greg KH

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

As exactly this (working with active contributors to help co-maintain the subsystem) has been brought at the ksummit maling list, I am just curious whether noone else actively working in that area was willing to step up?

	$ ./scripts/get_maintainer.pl --git -f security/
	James Morris <[email protected]> (supporter:SECURITY SUBSYSTEM)
   ...
Quoted 8 lines
Quoted 2 lines

If not, then I think this can be shown as a prime example why the problem of "non-substituability" of many maintainers is actually real.

Once several of us became aware that James was stepping away for a few weeks (I should mention this was not a planned absence and took most of us by surprise) we had a brief discussion off-list and several of us did offer to "step-up"; Serge had already created a repo and since he had pushed patches while James was away in the past it seemed a reasonable approach this time around.

That's great, as the communication around this has not been very much (an non-existant on the subsystem mailing list) I was not aware of it.

Quoted 6 lines

If Serge wants to do this, and as he has been the stand-in for James in the past, I have _no_ objection to this at all.

Serge, feel free to resend your patches to Linus if he doesn't pick them up in a few days, with the information that you are doing this in James's absence for a while.

Will do (and wil cc: lsm).

Quoted 2 lines

So, that was easy, I don't have to do this at all, great.

Quoted 8 lines
Quoted 3 lines
Quoted 1 line
Quoted 1 line

greg k-h

How can I verify that the pull James accepted from me is moving forward somehow? Or, if it isn't, where does it go now?

You can see it at
https://git.kernel.org/cgit/linux/kernel/git/sergeh/linux-security.git/log/security/smack?h=serge-next-1
As Greg suggested if Linus doesn't pull it in a few days I will resend the pull request.

Looks great. Thanks.

#16 lore raw
In reply to Greg KH
Quoted 6 lines · Greg KH

Hi all,

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

Quoted 6 lines

I'll take his git tree on kernel.org and push those to Linus for 3.16-rc1, as those look like they have had proper testing in linux-next.

But there only seems to be 14 patches in there. Are there pending patches that people have been sending and need to get in besides those?

Thanks for stepping up.

I had to take urgent leave and was unable to access email until this week.

We really should have a co-maintainer for the security subsystem -- please feel free to nominate someone.

There are several good candidates, including Serge, Kees and Paul Moore.

- James

Signature · 2 lines
James Morris
<[email protected]>
author
#17 lore raw
Quoted 15 lines · James Morris
Quoted 6 lines · Greg KH

Hi all,

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

Quoted 6 lines

I'll take his git tree on kernel.org and push those to Linus for 3.16-rc1, as those look like they have had proper testing in linux-next.

But there only seems to be 14 patches in there. Are there pending patches that people have been sending and need to get in besides those?

Quoted 8 lines

Thanks for stepping up.

I had to take urgent leave and was unable to access email until this week.

We really should have a co-maintainer for the security subsystem -- please feel free to nominate someone.

There are several good candidates, including Serge, Kees and Paul Moore.

As Serge has done it in the past when you are on vacation, I suggest he continue doing it.

thanks,

greg k-h

#18 lore raw
Quoted 20 lines · Greg KH
Quoted 19 lines · James Morris
Quoted 6 lines · Greg KH

Hi all,

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

Quoted 6 lines

I'll take his git tree on kernel.org and push those to Linus for 3.16-rc1, as those look like they have had proper testing in linux-next.

But there only seems to be 14 patches in there. Are there pending patches that people have been sending and need to get in besides those?

Thanks for stepping up.

I had to take urgent leave and was unable to access email until this week.

Quoted 7 lines
Quoted 4 lines

We really should have a co-maintainer for the security subsystem -- please feel free to nominate someone.

There are several good candidates, including Serge, Kees and Paul Moore.

As Serge has done it in the past when you are on vacation, I suggest he continue doing it.

As long as Serge agrees, that sounds good.

Mimi

#19 lore raw
Quoted 24 lines · Mimi Zohar
Quoted 23 lines · Greg KH
Quoted 22 lines · James Morris
Quoted 6 lines · Greg KH

Hi all,

James has had to step back from doing kernel work for a few weeks, so I've offered to step up and handle the security patches to get shuttled to Linus for merging for a while.

Quoted 6 lines

I'll take his git tree on kernel.org and push those to Linus for 3.16-rc1, as those look like they have had proper testing in linux-next.

But there only seems to be 14 patches in there. Are there pending patches that people have been sending and need to get in besides those?

Thanks for stepping up.

I had to take urgent leave and was unable to access email until this week.

We really should have a co-maintainer for the security subsystem -- please feel free to nominate someone.

Quoted 6 lines
Quoted 4 lines
Quoted 1 line

There are several good candidates, including Serge, Kees and Paul Moore.

As Serge has done it in the past when you are on vacation, I suggest he continue doing it.

As long as Serge agrees, that sounds good.

Sure, happy to do help however I can.

-serge