netdev - Re: [PATCH] openvswitch: Make IPv6 packet parsing dependent on IPv6 config

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAEP_g=9aOQ=B35dufSv8crw1OPZB=n21+QU04W96ak-A0GYaMg@mail.gmail.com>
Date:	Fri, 16 Nov 2012 09:36:53 -0800
From:	Jesse Gross <jesse@...ira.com>
To:	Vlad Yasevich <vyasevic@...hat.com>
Cc:	dev@...nvswitch.org, netdev@...r.kernel.org, davem@...emloft.net,
	fengguang.wu@...el.com
Subject: Re: [PATCH] openvswitch: Make IPv6 packet parsing dependent on IPv6 config

On Fri, Nov 16, 2012 at 7:40 AM, Vlad Yasevich <vyasevic@...hat.com> wrote:
> Openvswitch attempts to use IPv6 packet parsing functions without
> any dependency on IPv6 (unlike every other place in kernel).  Pull
> the IPv6 code in openvswitch togeter and put a conditional that's
> dependent on CONFIG_IPV6.
>
> Resolves:
> net/built-in.o: In function `ovs_flow_extract':
> (.text+0xbf5d5): undefined reference to `ipv6_skip_exthdr'
>
> Signed-off-by: Vlad Yasevich <vyasevic@...hat.com>

(Sorry for duplicates received, the original message had a typo in the
mailing list address.)

Doesn't this move in the opposite direction of your patches to make
IPv6 GSO/GRO always available?  The packets being processed here are
generally created by the guest but with Open vSwitch running on the
host.  Also, ipv6_skip_exthdr() is in exthdrs_core.c, so it actually
is always available.  I suspect that the real problem is that the
dependency on the ipv6 directory changed to CONFIG_INET and Open
vSwitch should now depend on this.
--
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