Bug#986619: linux-image-5.10.0-5-amd64: bonding broken on 5.10.0-5 (5.10.26)

[Salvatore Bonaccorso <carnil@debian.org>]

Source: linux
Source-Version: 5.10.28-1

On Thu, Apr 08, 2021 at 10:23:55AM +0300, Lauri Tirkkonen wrote:
> Package: src:linux
> Version: 5.10.26-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I have a bonding setup as follows:
> 
> 	% head -99 /etc/systemd/network/*
> 	==> /etc/systemd/network/bond0.netdev <==
> 	[NetDev]
> 	Name=bond0
> 	Kind=bond
> 
> 	[Bond]
> 	Mode=active-backup
> 	PrimaryReselectPolicy=always
> 	MIIMonitorSec=1s
> 
> 	==> /etc/systemd/network/bond0.network <==
> 	[Match]
> 	Name=bond0
> 
> 	[Network]
> 	DHCP=yes
> 	LLMNR=false
> 
> 	==> /etc/systemd/network/wired.network <==
> 	[Match]
> 	Name=enp*
> 
> 	[Link]
> 	RequiredForOnline=no
> 
> 	[Network]
> 	Bond=bond0
> 	PrimarySlave=true
> 
> 	==> /etc/systemd/network/wireless.network <==
> 	[Match]
> 	Name=wlan*
> 
> 	[Link]
> 	RequiredForOnline=no
> 
> 	[Network]
> 	Bond=bond0
> 
> on 5.10.0-4, this works fine. On 5.10.0-5, networkd is able to get an
> IPv4 address from DHCP on bond0, but not v6, and not even ping responses
> arrive from my gateway. The underlying devices work fine on both kernel
> versions.
> 
> I believe this is fixed in 5.10.27 with commit
> 36478a9ec5afd4efd031527d0371bf8f61e5aa91; see
> https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.27
> 
> Please update to 5.10.27 or backport the patch in question.

This is fixed with the 5.10.28-1 upload.

Regards,
Salvatore