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:	Sat, 25 Oct 2008 13:05:31 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	"Serge E. Hallyn" <serue@...ibm.com>
Cc:	David Howells <dhowells@...hat.com>,
	lkml <linux-kernel@...r.kernel.org>, jmorris@...ibm.com
Subject: Re: [PATCH] User namespaces: set of cleanups (v2)

Hi Serge,

On Fri, 24 Oct 2008 12:48:38 -0500 "Serge E. Hallyn" <serue@...ibm.com> wrote:
>
> would you mind applying the patch below behind
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/cred-2.6.git#creds-v3?
> 
> Assuming David has no objections?
> 
> I've just tested with David's plain creds-v3 tree and had no problems.
> (compiled with CONFIG_USER_NS=y|n and CONFIG_KEYS=y|n, boot+ltp with
> both =y)
> 
> Or would it fit your model better if I found a place to keep a quilt
> patchset or git tree?

Better if you can set up a git tree (or quilt series) somewhere as I
intend to only carry fixup patches myself in linux-next (so far).  Also
that means when you update your patches, I will just fetch them
automatically.

If this stuff depends on David's work, then I need to know that
explicitly so I can do ordering.  If it depends closely (i.e. changes in
Davids tree need to be reflected in yours) then you and David need to
come to some arrangement (maybe David could host your tree as a branch of
his (managing conflicts/updates).

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ