public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: linux-kernel@vger.kernel.org
Cc: ebiederm@xmission.com, htejun@gmail.com,
	linux-fsdevel@vger.kernel.org, gregkh@suse.de
Subject: [RFC] netns / sysfs interaction
Date: Mon, 7 Jan 2008 07:23:01 +0000	[thread overview]
Message-ID: <20080107072301.GW27894@ZenIV.linux.org.uk> (raw)

	As much as I hate to touch either subject, let alone both at
once...  Eric, would you mind explaining what exactly do you want
sysfs to do in presense of your "namespaces"?  On the "what does user
see if we do <...>" level.

	a) what happens if I do chdir("/sys/class/net/eth42/") and then
migrate?

	b) what happens to /sys/class/net/eth0/device visibility/things
it points to/etc.?

	c) what happens to open files?  E.g. to /sys/class/net - say it,
if migration happens between two getdents(2).

	d) what happens to visibility in other parts of sysfs?  E.g. to
things like
$ ls  /sys/devices/pci0000\:00/0000\:00\:0a.0/
bus     device  local_cpus  power      resource1         uevent
class   driver  modalias    resource   subsystem_device  vendor
config  irq     net:eth0    resource0  subsystem_vendor
$
See that net:eth0 in there?  Are all such suckers seen?

	e) while we are at it, wouldn't seeing the information in
/sys/devices/pci in general defeat whatever purpose you have in mind
for your stuff?

Context: we need sane locking for sysfs.  I think I have a more or less
workable scheme, but its feasibility depends big way on what netns needs
to have.

             reply	other threads:[~2008-01-07  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07  7:23 Al Viro [this message]
2008-01-07 10:01 ` [RFC] netns / sysfs interaction Eric W. Biederman
2008-01-07 10:24   ` Al Viro

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=20080107072301.GW27894@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@suse.de \
    --cc=htejun@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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