[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57652c0b-ded8-8386-c9a7-40deb1525db2@gmail.com>
Date: Thu, 29 Jul 2021 11:28:26 -0600
From: David Ahern <dsahern@...il.com>
To: Rocco Yue <rocco.yue@...iatek.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
Subject: Re: [PATCH net-next] net: ipv6: add IFLA_RA_MTU to expose mtu value
in the RA message
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.
Powered by blists - more mailing lists