netdev - Re: [RFC] IPv6 route replacement

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] [day] [month] [year] [list]

Date:	Wed, 22 Jul 2009 20:09:10 +0900
From:	YOSHIFUJI Hideaki <yoshfuji@...ux-ipv6.org>
To:	Jiri Pirko <jpirko@...hat.com>
CC:	netdev@...r.kernel.org, davem@...emloft.net, pekkas@...core.fi,
	kaber@...sh.net, yoshfuji@...ux-ipv6.org
Subject: Re: [RFC] IPv6 route replacement

Hi,

Jiri Pirko wrote:
> Now do you think this is the right behaviour? I would expect the first route to
> be replaced. The same result is when you do "ip -6 route replace"

Well, even in IPv4 you cannot change metric;
same route can be installed e.g., for manual
backup route entry.

But well, NLM_F_REPLACE handler is completely
missing in IPv6.  I think we are okay with
"replace" (NLM_F_CREATE|NLM_F_REPLACE) but we
could return "no such route" for "change"
(NLM_F_REPLACE).

--yoshfuji
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html