[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a4282d46-4c17-b395-dec0-7c8ac10cbf97@gmail.com>
Date: Mon, 3 Sep 2018 21:11:30 -0600
From: David Ahern <dsahern@...il.com>
To: Christian Brauner <christian@...uner.io>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: davem@...emloft.net, kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org,
pombredanne@...b.com, kstewart@...uxfoundation.org,
gregkh@...uxfoundation.org, fw@...len.de, ktkhai@...tuozzo.com,
lucien.xin@...il.com, jakub.kicinski@...ronome.com,
jbenc@...hat.com, nicolas.dichtel@...nd.com
Subject: Re: [PATCH net-next v1 3/5] ipv4: enable IFA_IF_NETNSID for
RTM_GETADDR
On 9/2/18 10:37 PM, Christian Brauner wrote:
> - Backwards Compatibility:
> If userspace wants to determine whether ipv4 RTM_GETADDR requests support
> the new IFA_IF_NETNSID property they should verify that the reply after
> sending a request includes the IFA_IF_NETNSID property. If it does not
> userspace should assume that IFA_IF_NETNSID is not supported for ipv4
> RTM_GETADDR requests on this kernel.
Can only use it once per message type, but NLM_F_DUMP_FILTERED is a flag
that can be set to explicitly say the request is filtered as requested.
See 21fdd092acc7e. I would like to see other filters added for addresses
in the same release this gets used. The only one that comes to mind for
addresses is to only return addresses for devices with master device
index N (same intent as 21fdd092acc7e for neighbors).
Powered by blists - more mailing lists