linux-kernel - Re: [GIT] New Credentials API (preliminary patches for 2.6.27) [updated]

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Xine.LNX.4.64.0807300841430.10277@us.intercode.com.au>
Date:	Wed, 30 Jul 2008 08:55:40 +1000 (EST)
From:	James Morris <jmorris@...ei.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	David Howells <dhowells@...hat.com>,
	Al Viro <viro@....linux.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: [GIT] New Credentials API (preliminary patches for 2.6.27)
 [updated]

On Tue, 29 Jul 2008, James Morris wrote:

> On Sat, 26 Jul 2008, James Morris wrote:
> 
> > A new credentials framework has been developed by David Howells.  The code 
> > has been through several iterations of posting and review, and is 
> > considered by various folk to be ready to merge into linux-next.
> 
> These patches have been updated by David to resolve conflicts in current 
> git, re-tested, and may be pulled cleanly per below.
> 

Linus,

Would you be able to provide some guidance on a strategy for getting these 
credentials changes merged?  I gather they've missed the boat for 2.6.27 
(although, they are now essentially reduced to API-level changes, and not 
as scary as they look).

Stephen is not keen on taking them in linux-next, as there'll be constant 
merge conflicts, and I'm not sure whether there'd be value in dropping 
them in at the end each day.

There seems to be two options at this stage:

1. Drop them into the front of linux-next and ask developers to maintain
trees against that.  Perhaps this is how API changes in general could 
happen?

2. Maintain them separately until the very start of the next merge window 
and get them in up front when it opens.

Thoughts?

- James
-- 
James Morris
<jmorris@...ei.org>
--
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/