[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5421C937.8040102@dev.mellanox.co.il>
Date: Tue, 23 Sep 2014 22:25:43 +0300
From: Eyal perry <eyalpe@....mellanox.co.il>
To: Tom Herbert <therbert@...gle.com>
CC: Eric Dumazet <eric.dumazet@...il.com>,
Andy Zhou <azhou@...ira.com>,
Linux Netdev List <netdev@...r.kernel.org>,
Or Gerlitz <ogerlitz@...lanox.com>,
Amir Vadai <amirv@...lanox.com>
Subject: Re: ip6_udp_tunnel fails to load
On 9/23/2014 7:55 PM, Tom Herbert wrote:
> On Tue, Sep 23, 2014 at 9:33 AM, Eyal perry <eyalpe@....mellanox.co.il> wrote:
>> On 9/23/2014 6:39 PM, Eric Dumazet wrote:
>>> On Tue, 2014-09-23 at 18:21 +0300, Eyal perry wrote:
>>>> Hello Andy,
>>>>
>>>> Lately I've start to observe a phenomena where the mlx4_en driver
>>>> couldn't load on my system as a result of an 'Unknown symbol in module'.
>>>>
>>>> [ 1277.458715] ip6_udp_tunnel: Unknown symbol ip6_local_out (err 0)
>>>> [ 1277.486810] ip6_udp_tunnel: Unknown symbol __put_net (err 0)
>>>>
>>>> Apparently, the mlx4_en driver is depend on the vxlan driver, which
>>>> depends on the ip6_udp_tunnel module which fails to load.
>>>>
>>>> 1. I've bisected this issue down to the following commit:
>>>> fd38441 udp_tunnel: Seperate ipv6 functions into its own file.
>>>>
>>>> 2. on a different host with a different .config, the module is loads
>>>> cleanly.
>>>>
>>>> 3. my sources are based on net-next commit
>>>> 6d967f8 udp_tunnel: Only build ip6_udp_tunnel.c when IPV6 is selected
>>>>
>>>> I'll send you both of the .config files in a private message.
>>>>
>>>> This issue is making any driver which is depend on vxlan/ip6_udp_tunnel
>>>> unusable, please take a look and fix
>>>
>>> Have you tried this patch ?
>>>
>>> https://patchwork.ozlabs.org/patch/392275/
>>>
>>> Thanks
>>
> Try https://patchwork.ozlabs.org/patch/392109/
>
> Tom
>
>> Hello Eric,
>>
>> Now I've tried but it still fails - the vxlan is still depends on the
>> ip6_udp_tunnel and it still fails to load because of the missing symbols
>> mentioned above.
>>
>>
>>
>>
>> --
>> 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
Thanks Tom, that solves my problem, though I can verify at the moment
that vxlan is well functioning.
--
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
Powered by blists - more mailing lists