netdev - Re: [PATCH net-next] net: vrf: Fix crash when IPv6 is disabled at boot time

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: <20160609.233458.1449029966409837912.davem@davemloft.net>
Date:	Thu, 09 Jun 2016 23:34:58 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dsa@...ulusnetworks.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] net: vrf: Fix crash when IPv6 is disabled at
 boot time

From: David Ahern <dsa@...ulusnetworks.com>
Date: Thu,  9 Jun 2016 10:21:00 -0700

> Frank Kellermann reported a kernel crash with 4.5.0 when IPv6 is
> disabled at boot using the kernel option ipv6.disable=1. Using
> current net-next with the boot option:
> 
> $ ip link add red type vrf table 1001
 ...
> The problem above is due to the fact that the fib hash table is not
> allocated when IPv6 is disabled at boot.
> 
> As for the VRF driver it should not do any IPv6 initializations if IPv6
> is disabled, so it needs to know if IPv6 is disabled at boot. The disable
> parameter is private to the IPv6 module, so provide an accessor for
> modules to determine if IPv6 was disabled at boot time.
> 
> Fixes: 35402e3136634 ("net: Add IPv6 support to VRF device")
> Signed-off-by: David Ahern <dsa@...ulusnetworks.com>

Applied.