Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20211020095707.GA16295@ircssh-2.c.rugged-nimbus-611.internal>
 <CAHNKnsRFah6MRxECTLNwu+maN0o9jS9ENzSAiWS4v1247BqYdg@mail.gmail.com> <20211020163417.GA21040@ircssh-2.c.rugged-nimbus-611.internal>
In-Reply-To: <20211020163417.GA21040@ircssh-2.c.rugged-nimbus-611.internal>
From:   Sergey Ryazanov <ryazanov.s.a@gmail.com>
Date:   Wed, 20 Oct 2021 23:02:17 +0300
Message-ID: <CAHNKnsSC3bfZQxpwqYfyw8bB06otaK8YWkgtZfFOnX9vMkOVgg@mail.gmail.com>
Subject: Re: Retrieving the network namespace of a socket
To:     Sargun Dhillon <sargun@sargun.me>
Cc:     LKML <linux-kernel@vger.kernel.org>,
        netdev <netdev@vger.kernel.org>,
        Christian Brauner <christian.brauner@ubuntu.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, Oct 20, 2021 at 7:34 PM Sargun Dhillon <sargun@sargun.me> wrote:
> On Wed, Oct 20, 2021 at 05:03:56PM +0300, Sergey Ryazanov wrote:
>> On Wed, Oct 20, 2021 at 12:57 PM Sargun Dhillon <sargun@sargun.me> wrote:
>>> I'm working on a problem where I need to determine which network namespace a
>>> given socket is in. I can currently bruteforce this by using INET_DIAG, and
>>> enumerating namespaces and working backwards.
>>
>> Namespace is not a per-socket, but a per-process attribute. So each
>> socket of a process belongs to the same namespace.
>>
> > Could you elaborate what kind of problem you are trying to solve?
>> Maybe there is a more simple solution. for it.
>
> That's not entirely true. See the folowing code:
>
> int main() {
>         int fd1, fd2;
>         fd1 = socket(AF_INET, SOCK_STREAM, 0);
>         assert(fd1 >= 0);
>         assert(unshare(CLONE_NEWNET) == 0);
>         fd2 = socket(AF_INET, SOCK_STREAM, 0);
>         assert(fd2 >= 0);
> }
>
> fd1 and fd2 have different sock_net.

Ouch, I totally missed this case. Thank you for reminding me.

--
Sergey