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]

Message-ID: <20081024191813.GA27505@us.ibm.com>
Date:	Fri, 24 Oct 2008 14:18:13 -0500
From:	"Serge E. Hallyn" <serue@...ibm.com>
To:	David Howells <dhowells@...hat.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	lkml <linux-kernel@...r.kernel.org>, jmorris@...ibm.com
Subject: Re: [PATCH] User namespaces: set of cleanups (v2)

Quoting David Howells (dhowells@...hat.com):
> Serge E. Hallyn <serue@...ibm.com> wrote:
> 
> > I've just tested with David's plain creds-v3 tree
> 
> Note the creds-v4 branch is now current.  Is it worth me replacing that with a
> tree that just has a master branch to simplify things?

I saw it in your list of branches, but linux-next/Next/Trees still
listed v3 so i figured i should test against that.

> > -	struct user_namespace *ns = current->nsproxy->user_ns;
> > +	struct user_namespace *ns = current_user()->user_ns;
> 
> current_user_ns() perchance?

Yes, thanks.  (Of course that doesn't break anything so if the patch is
otherwise ok i've written down a note to send a follow-up patch)

thanks,
-serge
--
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/