[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANaxB-wvJsts7RUEg1pouD0xMLTQAoVMaWaXZ2wLFT9XE1E1Mw@mail.gmail.com>
Date: Sat, 22 Oct 2016 00:37:01 -0700
From: Andrey Vagin <avagin@...nvz.org>
To: Cong Wang <xiyou.wangcong@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Linux Containers <containers@...ts.linux-foundation.org>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
"Eric W . Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH] net: skip genenerating uevents for network namespaces
that are exiting
Hi Cong,
On Thu, Oct 20, 2016 at 10:25 PM, Andrey Vagin <avagin@...nvz.org> wrote:
> On Thu, Oct 20, 2016 at 8:10 PM, Cong Wang <xiyou.wangcong@...il.com> wrote:
>> On Thu, Oct 20, 2016 at 7:46 PM, Andrei Vagin <avagin@...nvz.org> wrote:
>>> No one can see these events, because a network namespace can not be
>>> destroyed, if it has sockets.
>>>
>>
>> Are you sure? kobject_uevent_env() seems sending uevents to all
>> network namespaces.
>
> kobj_bcast_filter() checks that a kobject namespace is equal to a
> socket namespace.
Today I've checked that it really works as I read from the source code.
I use this tool to read events:
https://gist.github.com/avagin/430ba431fc2972002df40ebe6a048b36
And I see that events from non-network devices are delivered to all sockets,
but events from network devices are delivered only to sockets from
a network namespace where a device is operated.
Thanks,
Andrei
>
>
>> _______________________________________________
>> Containers mailing list
>> Containers@...ts.linux-foundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/containers
Powered by blists - more mailing lists