From: Marc Harvey <[email protected]> Date: Wed, 8 Apr 2026 17:10:05 -0700 > On Wed, Apr 8, 2026 at 9:40 AM Jakub Kicinski <[email protected]> wrote: > > > > It pains me to report on non-debug kernels: > > I'm sorry to have pained you. Despite my best efforts to run with the > exact same environment and conditions as your CI, my teamd can be > killed with "teamd -k" but yours hangs (both are version 1.32 on > Fedora with the same kernel config).
Considering the subsequent "kill" works on the dbg instance (thanks to 2400s timeout), I guess teamd is somehow stuck at SIGTERM handling removing team devices in teamd_port_remove_all(). (SIGTERM being masked sounds unlikely) https://netdev-ctrl.bots.linux.dev/logs/vmksft/bonding-dbg/results/593802/4-teamd-activebackup-sh/stdout https://netdev-ctrl.bots.linux.dev/logs/vmksft/bonding-dbg/results/593802/4-teamd-activebackup-sh/stderr ---8<--- [ 759.819815][T21724] test_team1: Port device eth1 removed [ 759.822323][T21724] test_team1: Port device eth0 removed [ 790.615687][T21728] test_team2: Port device eth1 removed [ 790.617445][T21728] test_team2: Port device eth0 removed ---8<--- Adding -N and letting "ip netns del" release the last netns refcnt and defer device destruction to cleanup_net() may help. > For v7, I’ll invoke "teamd -k" > using the timeout utility, or just increase the test timeout. +1 for the latter, maybe set timeout=300. daemon_pid_file_kill_wait(SIGTERM, 30) * 2 = 120s, but just in case. See these files for howto: $ find tools/testing/selftests/net/ -name settings
