netdev - Re: [PATCH] ipv6: fix RTPROT_RA markup of RA routes w/nexthops

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]

Message-Id: <20120716.225611.1570342975310166446.davem@davemloft.net>
Date:	Mon, 16 Jul 2012 22:56:11 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	infrastation@...dex.ru
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] ipv6: fix RTPROT_RA markup of RA routes w/nexthops

From: Denis Ovsienko <infrastation@...dex.ru>
Date: Tue, 10 Jul 2012 18:45:50 +0400

> From: Denis Ovsienko <infrastation@...dex.ru>
> 
> Userspace implementations of network routing protocols sometimes need to
> tell RA-originated IPv6 routes from other kernel routes to make proper
> routing decisions. This makes most sense for RA routes with nexthops,
> namely, default routes and Route Information routes.
> 
> The intended mean of preserving RA route origin in a netlink message is
> through indicating RTPROT_RA as protocol code. Function rt6_fill_node()
> tried to do that for default routes, but its test condition was taken
> wrong. This change is modeled after the original mailing list posting
> by Jeff Haran. It fixes the test condition for default route case and
> sets the same behaviour for Route Information case (both types use
> nexthops). Handling of the 3rd RA route type, Prefix Information, is
> left unchanged, as it stands for interface connected routes (without
> nexthops).
> 
> Signed-off-by: Denis Ovsienko <infrastation@...dex.ru>

Applied to net-next, thanks.
--
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