All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Thery <benjamin.thery-6ktuUTfB/bM@public.gmane.org>
To: "Eric W. Biederman"
	<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>,
	Pavel Emelyanov <xemul-3ImXcnM4P+0@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: nets: status of sysfs with netns
Date: Fri, 14 Mar 2008 16:38:18 +0100	[thread overview]
Message-ID: <47DA9BEA.9070907@bull.net> (raw)

Eric, Pavel,

I haven't followed everything about the sysfs/netns issue recently and I 
think I have missed some of its recent developments in the past weeks. 
So I'm wondering what is the current status? Is anyone still working on it?

As several netns patches for IPv4 and IPv6 have already been merged in 
net-2.6.26, it would be great to have the sysfs part also to help people 
who want test netns.
Right now, it is a pain to boot and test a system with CONFIG_SYSFS=n.

(I know the problem is not trivial and won't be easy to solve. I just 
want to be sure it is not forgotten)

Pavel, I've heard you sent (or have) a patch that prevents sysfs access 
from a "child" netns. A patch that can be a good workaround until we 
have the full thing ready. I can't find it in mailing lists archives, 
can you give some hints about where to find it? :)

Thanks a lot.

Benjamin

-- 
B e n j a m i n   T h e r y  - BULL/DT/Open Software R&D

    http://www.bull.com

             reply	other threads:[~2008-03-14 15:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14 15:38 Benjamin Thery [this message]
     [not found] ` <47DA9BEA.9070907-6ktuUTfB/bM@public.gmane.org>
2008-03-14 15:44   ` nets: status of sysfs with netns Pavel Emelyanov
     [not found]     ` <47DA9D71.2010707-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-03-14 15:54       ` Benjamin Thery
2008-03-18 17:01       ` Eric W. Biederman
     [not found]         ` <m1lk4gufto.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2008-04-11 15:33           ` Daniel Lezcano

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=47DA9BEA.9070907@bull.net \
    --to=benjamin.thery-6ktuutfb/bm@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
    --cc=xemul-3ImXcnM4P+0@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.