public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, dev@sw.ru, herbert@13thfloor.at,
	devel@openvz.org, ebiederm@xmission.com, xemul@sw.ru,
	Dave Hansen <haveblue@us.ibm.com>, Andrew Morton <akpm@osdl.org>,
	Cedric Le Goater <clg@fr.ibm.com>,
	serue@us.ibm.com
Subject: Re: [PATCH] namespaces: uts_ns: make information visible via	/proc/PID/uts directory
Date: Tue, 23 May 2006 11:07:00 +1200	[thread overview]
Message-ID: <44724414.5020505@vilain.net> (raw)
In-Reply-To: <1148298318.17376.19.camel@localhost.localdomain>

Alan Cox wrote:

>On Llu, 2006-05-22 at 17:24 +1200, Sam Vilain wrote:
>  
>
>>From: Sam Vilain <sam.vilain@catalyst.net.nz>
>>
>>Export the UTS information to a per-process directory /proc/PID/uts,
>>that has individual nodes for hostname, ostype, etc - similar to
>>those in /proc/sys/kernel
>>    
>>
>
>Can you explain the locking being used here against the name being
>changed at the same moment ?
>

Is this a test?  :-)

Let's see, get_task_pid locks the task struct (so that it doesn't go
away while we're de-referencing the nsproxy and uts_ns etc), and the
kobj references are assumed to be enough to avoid the references
dropping away in the meantime.

I didn't grab uts_sem.  That semaphore could be made per-uts_ns, in
theory.  Whether anyone cares about contention that much is another
question.

I intended this to be exploratory, it wasn't really mergable.  Should
have added an [RFC] tag, sorry about that.

Sam.

  reply	other threads:[~2006-05-22 23:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22  5:24 [PATCH] namespaces: uts_ns: make information visible via /proc/PID/uts directory Sam Vilain
2006-05-22  8:04 ` Andrew Morton
2006-05-22 21:31   ` Sam Vilain
2006-05-22 11:45 ` Alan Cox
2006-05-22 23:07   ` Sam Vilain [this message]
2006-05-22 23:10     ` Sam Vilain
2006-05-22 23:49       ` Sam Vilain
2006-05-22 14:03 ` Herbert Poetzl
2006-05-22 16:39 ` Eric W. Biederman
2006-05-22 23:18   ` Sam Vilain
  -- strict thread matches above, loose matches on Subject: below --
2006-05-22  5:23 Sam Vilain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44724414.5020505@vilain.net \
    --to=sam@vilain.net \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=clg@fr.ibm.com \
    --cc=dev@sw.ru \
    --cc=devel@openvz.org \
    --cc=ebiederm@xmission.com \
    --cc=haveblue@us.ibm.com \
    --cc=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.com \
    --cc=xemul@sw.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox