[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180125233043.66ff08c2@redhat.com>
Date: Thu, 25 Jan 2018 23:30:43 +0100
From: Jiri Benc <jbenc@...hat.com>
To: Nicolas Dichtel <nicolas.dichtel@...nd.com>
Cc: Christian Brauner <christianvanbrauner@...il.com>,
netdev@...r.kernel.org, ebiederm@...ssion.com, davem@...emloft.net,
dsahern@...il.com, fw@...len.de, daniel@...earbox.net,
lucien.xin@...il.com, mschiffer@...verse-factory.net,
jakub.kicinski@...ronome.com, vyasevich@...il.com,
linux-kernel@...r.kernel.org, w.bumiller@...xmox.com,
Christian Brauner <christian.brauner@...ntu.com>
Subject: Re: [PATCH net-next 0/3 V1] rtnetlink: enable IFLA_IF_NETNSID for
RTM_{DEL,SET}LINK
On Thu, 25 Jan 2018 15:20:59 +0100, Nicolas Dichtel wrote:
> Hmm, I don't agree. For me, it would be the correct answer. If user has a socket
> in ns_a and targets a RTM_GETLINK in ns_b, the answer he gets should be like if
> it was done in ns_b.
But that information would be useless for the caller. Why return a
value that has no meaning for the caller and can not be used? More so
when the kernel is aware of what the correct meaningful value is?
> This is already the case with messages received with NETLINK_LISTEN_ALL_NSID,
> there is no reason to do something different.
NETLINK_LISTEN_ALL_NSID is tough due to way it is implemented. But yes,
it should translate the netnsids to be valid in the socket's netns.
That's the only sane way for the listener.
Jiri
Powered by blists - more mailing lists