linux-kernel - Re: [GIT] Security subsystem upate for 3.18

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6097685.yy4GYjPioe@sifl>
Date:	Mon, 13 Oct 2014 09:07:53 -0400
From:	Paul Moore <pmoore@...hat.com>
To:	James Morris <jmorris@...ei.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LSM List <linux-security-module@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [GIT] Security subsystem upate for 3.18

On Monday, October 13, 2014 03:06:34 PM James Morris wrote:
> On Sun, 12 Oct 2014, Linus Torvalds wrote:
> > on some previous development, so it's often a good time to simply
> > create a new feature branch. I don't know how James feels about
> > merging multiple separate feature branches, but I know that *I* tend
> > to appreciate it when I get multiple well-defined pull requests rather
> > than one big one that does many different things.
> 
> It's fine with me.
> 
> This is the first time I saw (or noticed) that Paul had back merged ahead
> of me, but it seemed to merge into my tree ok so I didn't query it at the
> time.

The management of the linux-security tree, the approach I was taking with the 
SELinux tree, and the approach that the other LSM maintainers use has been 
discussed many times on the LSM list.  I'm also fairly certain that you were 
on the To/CC line for many, if not all, of those threads.

-- 
paul moore
security and virtualization @ redhat

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/