netdev - Upgrade from linux-lts-5.10.25 to linux-lts 5.10.26 breaks bonding.

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>] [day] [month] [year] [list]

Message-ID: <69e1d825-db19-3d05-5406-b1c2774528f7@nurealm.net>
Date:   Sat, 27 Mar 2021 10:59:29 -0600
From:   James Feeney <james@...ealm.net>
To:     Jay Vosburgh <j.vosburgh@...il.com>,
        Veaceslav Falico <vfalico@...il.com>,
        Andy Gospodarek <andy@...yhouse.net>
Cc:     netdev@...r.kernel.org
Subject: Upgrade from linux-lts-5.10.25 to linux-lts 5.10.26 breaks bonding.

Arch linux-lts-5.10.25-1 to linux-lts 5.10.26-1

This is on a wireless bonding setup with fallback to wired ethernet.  Everything with the interfaces looks fine, except, for instance, ping returns the error message "ping: sendmsg: Invalid argument".  Of course, networking becomes unusable.

Removing the bonding interface, and adding an IP address directly to either wired or wireless interface, networking works normally.

This is not to do with the linux-firmware package, where downgrading linux-firmware makes no difference.

Downgrading the kernel resolves the problem, but I don't see any bonding commits between linux-lts-5.10.25 and linux-lts 5.10.26.

Any thoughts, shy of performing a full bisect, would be appreciated.

James