[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210730173946.31205-1-rocco.yue@mediatek.com>
Date: Sat, 31 Jul 2021 01:39:46 +0800
From: Rocco Yue <rocco.yue@...iatek.com>
To: David Ahern <dsahern@...il.com>
CC: "David S . Miller" <davem@...emloft.net>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
David Ahern <dsahern@...nel.org>,
Jakub Kicinski <kuba@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>, <rocco.yue@...il.com>,
Rocco Yue <rocco.yue@...iatek.com>
Subject: Re: [PATCH net-next] net: ipv6: add IFLA_RA_MTU to expose mtu value in the RA message
On Thu, 2021-07-29 at 11:28 -0600, David Ahern wrote:
On 7/29/21 9:42 AM, Rocco Yue wrote:
>> Because the purpose of this patch is for userspace to correctly read the
>> ra_mtu value of different network device, if the DEVCONF is completely dropped,
>> does that mean I can add the "ra_mtu" member in the "struct net_device" .
>
> good point. IFLA is the wrong attribute. It should be IFLA_INET6_RA_MTU,
> stored in inet6_dev and added to the link message in
> inet6_fill_ifla6_attrs.
will do, thanks for your suggestion.
Powered by blists - more mailing lists