From: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
To: Andi Kleen <andi@firstfloor.org>
Cc: netdev@vger.kernel.org, xemul@openvz.org,
virtualization@lists.linux-foundation.org
Subject: Re: netlink versus pid namespaces
Date: Fri, 15 Oct 2010 19:19:03 +0400 [thread overview]
Message-ID: <20101015151903.GA3487@ms2.inr.ac.ru> (raw)
In-Reply-To: <20101015142357.GA29321@basil.fritz.box>
Hello!
> netlink uses pids (or really tids I hope?) to address sockets
> associated with processes.
Not really. It uses port number which is called "pid" occasionally. Bad name.
Autobind function simply selects tgid of calling process as the first guess.
Actually sockets are addressed by pair (net namespace, port) and
communication is possible only inside net namespace. So, communication
between namespaces is already prohibited.
pid namespaces do not participate in the picture at all.
Alexey
next prev parent reply other threads:[~2010-10-15 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 14:23 netlink versus pid namespaces Andi Kleen
2010-10-15 15:19 ` Alexey Kuznetsov [this message]
2010-10-15 15:23 ` Andi Kleen
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=20101015151903.GA3487@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=andi@firstfloor.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xemul@openvz.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;
as well as URLs for NNTP newsgroup(s).