From: Serge Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
Cc: Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Subject: Re: setns vs unshare bug
Date: Fri, 10 Aug 2012 10:00:46 -0500 [thread overview]
Message-ID: <20120810150046.GA20449@sergelap> (raw)
In-Reply-To: <502520E8.5040401-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
Hi Pavel,
I don't believe this is a bug. The fd is to a specific network
namespace. If the target task later changes his namespace, that
doesn't change the fact that you asked for access to the old
namespace.
You're worried about a race?
-serge
Quoting Pavel Emelyanov (xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org):
> Hi, Eric!
>
> There's an issue with setns versus unshare syscall which I consider
> to be worth looking at. Look -- when you open some task's namespace file,
> e.g. /proc/<pid>/ns/net, the net namespace is cached on the proc inode.
>
> If later the task with the pid <pid> unshares the namespace in question
> (in this case -- net ns) the subsequent openings of this task's proc ns
> file will result in old namespace obtained and the setns call will not
> work as expected. Here's a simple proggie which demonstrates this:
>
> int main(void)
> {
> int pid, fd;
> char path[64];
>
> pid = fork();
> if (!pid) {
> fd = open("/proc/self/ns/net", O_RDONLY);
> close(fd);
> unshare(CLONE_NEWNET);
> printf("New net:\n");
> system("ip l");
> sleep(1);
> } else {
> sleep(1);
> printf("Old net:\n");
> system("ip l");
> sprintf(path, "/proc/%d/ns/net", pid);
> fd = open(path, O_RDONLY);
> set_ns(fd, CLONE_NEWNET);
> printf("New net 2:\n");
> system("ip l");
> }
>
> return 0;
> }
>
> The "else" branch after set_ns expects the net it set to be the new one (and
> contain a lo device only), but it's not so -- after the setns syscall the net
> namespace isn't changed! If you comment out the "if" branch's open and close
> calls (thus avoiding the ns caching) the setns works as expected.
>
> I assume you're aware of this problem, so do you have plans to fix this?
>
> Thanks,
> Pavel
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linuxfoundation.org/mailman/listinfo/containers
next prev parent reply other threads:[~2012-08-10 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 14:55 setns vs unshare bug Pavel Emelyanov
[not found] ` <502520E8.5040401-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2012-08-10 15:00 ` Serge Hallyn [this message]
2012-08-10 15:08 ` Pavel Emelyanov
[not found] ` <502523DF.4040103-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2012-08-10 15:17 ` Pavel Emelyanov
[not found] ` <502525FC.3060608-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2012-08-10 15:24 ` Serge Hallyn
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=20120810150046.GA20449@sergelap \
--to=serge.hallyn-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=xemul-bzQdu9zFT3WakBO8gow8eQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox