linux-kernel - Re: [PATCH] User namespaces: set of cleanups (v2)

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]

Date:	Sun, 26 Oct 2008 11:07:53 +0000
From:	David Howells <dhowells@...hat.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	dhowells@...hat.com, "Serge E. Hallyn" <serue@...ibm.com>,
	lkml <linux-kernel@...r.kernel.org>, jmorris@...ibm.com
Subject: Re: [PATCH] User namespaces: set of cleanups (v2)

Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> It would be good if you could have a "next" (or "creds-next" or
> something) branch in your tree and I can fetch that (that way I don't
> have to keep updating my configs).  It is OK if thet branch rebases and
> may just be an alias for another branch (or a subset if you have
> experimental stuff in there.  Remember "posted, reviewed, tested before
> it is in linux-next".

Those patches aren't likely to change much, and they get hit with LTP
regularly.

What base for the patches?  Linus's head?

David
--
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/