lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 15 Sep 2023 18:02:02 +0800
From: Hangbin Liu <liuhangbin@...il.com>
To: David Ahern <dsahern@...nel.org>
Cc: Nicolas Dichtel <nicolas.dichtel@...nd.com>, netdev@...r.kernel.org,
	"David S . Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	Ido Schimmel <idosch@...sch.org>,
	Thomas Haller <thaller@...hat.com>
Subject: Re: [PATCH net-next] ipv6: do not merge differe type and protocol
 routes

On Thu, Sep 14, 2023 at 09:08:18PM -0600, David Ahern wrote:
> On 9/14/23 8:23 PM, Hangbin Liu wrote:
> > On Fri, Sep 01, 2023 at 11:36:51AM +0200, Nicolas Dichtel wrote:
> >>> I do agree now that protocol is informative (passthrough from the kernel
> >>> perspective) so not really part of the route. That should be dropped
> > 
> > I'm not sure. Is there any user space route daemon will use this info? e.g. some
> > BGP route daemon?
> 
> It is passthrough information for userspace to track who installed the
> route. It is not part of the route itself, but metadata passed in and
> returned.

Thanks. I will drop this info.

Hangbin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ