netdev - Re: [PATCH net-next v2] ipv6: remove old conditions on flow label sharing

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: <20131105.144133.43837121028952798.davem@davemloft.net>
Date:	Tue, 05 Nov 2013 14:41:33 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	florent.fourcot@...t-bretagne.fr
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2] ipv6: remove old conditions on flow label
 sharing

From: Florent Fourcot <florent.fourcot@...t-bretagne.fr>
Date: Sat,  2 Nov 2013 14:55:07 +0100

> The code of flow label in Linux Kernel follows
> the rules of RFC 1809 (an informational one) for
> conditions on flow label sharing. There rules are
> not in the last proposed standard for flow label
> (RFC 6437), or in the previous one (RFC 3697).
> 
> Since this code does not follow any current or
> old standard, we can remove it.
> 
> With this removal, the ipv6_opt_cmp function is
> now a dead code and it can be removed too.
> 
> Changelog to v1:
>  * add justification for the change
>  * remove the condition on IPv6 options
> 
> Signed-off-by: Florent Fourcot <florent.fourcot@...t-bretagne.fr>

Applied, but I had to also remove ipv6_hdr_cmp() as that became unused
as well.

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