Re: [GIT] Security subsystem updates for 3.13

2013-11-24 Thread James Morris
Sorry about all this -- we'll do better next time. -- James Morris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at

Re: [GIT] Security subsystem updates for 3.13

2013-11-24 Thread James Morris
Sorry about all this -- we'll do better next time. -- James Morris jmor...@namei.org -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the

Re: [GIT] Security subsystem updates for 3.13

2013-11-23 Thread Linus Torvalds
On Fri, Nov 22, 2013 at 12:25 PM, David Howells wrote: > Linus Torvalds wrote: > >> So for future cases: if there are big independent overhauls of core >> subsystems, I'd really like to see them kept separate, ok? > > Since the trusted and encrypted keys that Mimi and Dmitry deal with are also >

Re: [GIT] Security subsystem updates for 3.13

2013-11-23 Thread Linus Torvalds
On Fri, Nov 22, 2013 at 12:25 PM, David Howells dhowe...@redhat.com wrote: Linus Torvalds torva...@linux-foundation.org wrote: So for future cases: if there are big independent overhauls of core subsystems, I'd really like to see them kept separate, ok? Since the trusted and encrypted keys

Re: [GIT] Security subsystem updates for 3.13

2013-11-22 Thread George Spelvin
On Thu, 21 Nov 2013, Linus Torvalds wrote: > I do see *some* minimal comments on it from George Spelvin on lkml. I'd like to apologize for dropping the ball on that. I started working on it seriously, but with various emergencies, I've been AFK from lkml for the last month. I'm not really

Re: [GIT] Security subsystem updates for 3.13

2013-11-22 Thread David Howells
Linus Torvalds wrote: > So for future cases: if there are big independent overhauls of core > subsystems, I'd really like to see them kept separate, ok? Since the trusted and encrypted keys that Mimi and Dmitry deal with are also more akin to the keyring stuff, should they go through the

Re: [GIT] Security subsystem updates for 3.13

2013-11-22 Thread Josh Boyer
On Thu, Nov 21, 2013 at 11:22 PM, Linus Torvalds wrote: > In short: this is exactly the kind of thing I *don't* enjoy merging, > because the code that needed review was > > - mixed up with other changes that had nothing to do with it > - had no pointers to help me review it > - had zero

Re: [GIT] Security subsystem updates for 3.13

2013-11-22 Thread James Morris
On Thu, 21 Nov 2013, Linus Torvalds wrote: > So for future cases: if there are big independent overhauls of core > subsystems, I'd really like to see them kept separate, ok? Yep. > So guys, make it easier for me to merge these kinds of things, and > *don't* do what happened this time. Ok?

Re: [GIT] Security subsystem updates for 3.13

2013-11-22 Thread James Morris
On Thu, 21 Nov 2013, Linus Torvalds wrote: So for future cases: if there are big independent overhauls of core subsystems, I'd really like to see them kept separate, ok? Yep. So guys, make it easier for me to merge these kinds of things, and *don't* do what happened this time. Ok? Pretty

Re: [GIT] Security subsystem updates for 3.13

2013-11-22 Thread Josh Boyer
On Thu, Nov 21, 2013 at 11:22 PM, Linus Torvalds torva...@linux-foundation.org wrote: In short: this is exactly the kind of thing I *don't* enjoy merging, because the code that needed review was - mixed up with other changes that had nothing to do with it - had no pointers to help me review

Re: [GIT] Security subsystem updates for 3.13

2013-11-22 Thread David Howells
Linus Torvalds torva...@linux-foundation.org wrote: So for future cases: if there are big independent overhauls of core subsystems, I'd really like to see them kept separate, ok? Since the trusted and encrypted keys that Mimi and Dmitry deal with are also more akin to the keyring stuff, should

Re: [GIT] Security subsystem updates for 3.13

2013-11-22 Thread George Spelvin
On Thu, 21 Nov 2013, Linus Torvalds wrote: I do see *some* minimal comments on it from George Spelvin on lkml. I'd like to apologize for dropping the ball on that. I started working on it seriously, but with various emergencies, I've been AFK from lkml for the last month. I'm not really

Re: [GIT] Security subsystem updates for 3.13

2013-11-19 Thread James Morris
Also, here's an updated branch to pull from with four new fixes from David. --- The following changes since commit be408cd3e1fef73e9408b196a79b9934697fe3b1: Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2013-11-04 06:40:55 -0800) are available in the git repository at:

Re: [GIT] Security subsystem updates for 3.13

2013-11-19 Thread James Morris
Also, here's an updated branch to pull from with four new fixes from David. --- The following changes since commit be408cd3e1fef73e9408b196a79b9934697fe3b1: Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2013-11-04 06:40:55 -0800) are available in the git repository at:

Re: [GIT] Security subsystem updates for 3.13

2013-11-18 Thread James Morris
On Mon, 18 Nov 2013, Linus Torvalds wrote: > On Mon, Nov 18, 2013 at 3:30 PM, James Morris wrote: > > On Mon, 18 Nov 2013, Josh Boyer wrote: > >> > >> Unless I'm missing something, I don't think this has landed in Linus' > >> tree yet. Linus, did this pull request get NAKed or fall through the

Re: [GIT] Security subsystem updates for 3.13

2013-11-18 Thread Linus Torvalds
On Mon, Nov 18, 2013 at 3:30 PM, James Morris wrote: > On Mon, 18 Nov 2013, Josh Boyer wrote: >> >> Unless I'm missing something, I don't think this has landed in Linus' >> tree yet. Linus, did this pull request get NAKed or fall through the >> cracks? > > I think Linus is on vacation and

Re: [GIT] Security subsystem updates for 3.13

2013-11-18 Thread James Morris
On Mon, 18 Nov 2013, Josh Boyer wrote: > On Wed, Nov 6, 2013 at 7:51 PM, James Morris wrote: > > In this patchset, we finally get an SELinux update, with Paul Moore taking > > over as maintainer of that code. > > > > Also a significant update for the Keys subsystem, as well as maintenance > >

Re: [GIT] Security subsystem updates for 3.13

2013-11-18 Thread James Morris
On Mon, 18 Nov 2013, Josh Boyer wrote: On Wed, Nov 6, 2013 at 7:51 PM, James Morris jmor...@namei.org wrote: In this patchset, we finally get an SELinux update, with Paul Moore taking over as maintainer of that code. Also a significant update for the Keys subsystem, as well as

Re: [GIT] Security subsystem updates for 3.13

2013-11-18 Thread Linus Torvalds
On Mon, Nov 18, 2013 at 3:30 PM, James Morris jmor...@namei.org wrote: On Mon, 18 Nov 2013, Josh Boyer wrote: Unless I'm missing something, I don't think this has landed in Linus' tree yet. Linus, did this pull request get NAKed or fall through the cracks? I think Linus is on vacation and

Re: [GIT] Security subsystem updates for 3.13

2013-11-18 Thread James Morris
On Mon, 18 Nov 2013, Linus Torvalds wrote: On Mon, Nov 18, 2013 at 3:30 PM, James Morris jmor...@namei.org wrote: On Mon, 18 Nov 2013, Josh Boyer wrote: Unless I'm missing something, I don't think this has landed in Linus' tree yet. Linus, did this pull request get NAKed or fall through

[GIT] Security subsystem updates for 3.13

2013-11-06 Thread James Morris
In this patchset, we finally get an SELinux update, with Paul Moore taking over as maintainer of that code. Also a significant update for the Keys subsystem, as well as maintenance updates to Smack, IMA, TPM, and Apparmor. Please pull. The following changes since commit

[GIT] Security subsystem updates for 3.13

2013-11-06 Thread James Morris
In this patchset, we finally get an SELinux update, with Paul Moore taking over as maintainer of that code. Also a significant update for the Keys subsystem, as well as maintenance updates to Smack, IMA, TPM, and Apparmor. Please pull. The following changes since commit