On Wed, 12 Jan 2022, Mat Martineau wrote: > On Mon, 10 Jan 2022, Geliang Tang wrote: > >> Added the test cases for MP_FAIL, use 'tc' command to trigger the >> checksum failure. >> >> Suggested-by: Davide Caratti >> Co-developed-by: Matthieu Baerts >> Signed-off-by: Matthieu Baerts >> Signed-off-by: Geliang Tang >> --- >> tools/testing/selftests/net/mptcp/config | 5 + >> .../testing/selftests/net/mptcp/mptcp_join.sh | 111 ++++++++++++++++-- >> 2 files changed, 107 insertions(+), 9 deletions(-) >> > > Does anyone else see the "leaked reference" errors when running these fail > tests with the latest export branch? Looks like the reference tracker finds a > tc-related error: > > [ 238.871372] leaked reference. > [ 238.872393] fl_change+0x2db/0x2520 > [ 238.873148] tc_new_tfilter+0x6c4/0x11f0 > [ 238.873959] rtnetlink_rcv_msg+0x49f/0x640 > [ 238.874798] netlink_rcv_skb+0xc4/0x1f0 > [ 238.875570] netlink_unicast+0x2d5/0x410 > [ 238.876364] netlink_sendmsg+0x3b3/0x6c0 > [ 238.877155] sock_sendmsg+0x91/0xa0 > [ 238.877890] ____sys_sendmsg+0x3ad/0x3f0 > [ 238.878684] ___sys_sendmsg+0xdb/0x140 > [ 238.879354] __sys_sendmsg+0xae/0x120 > [ 238.879947] do_syscall_64+0x3b/0x90 > [ 238.880683] entry_SYSCALL_64_after_hwframe+0x44/0xae > > It doesn't look like MPTCP is to blame, but I'm curious if others see the > same. I've attached my kernel config as Davide requested in the meeting today. I had applied this version of the "Clarify when options can be used" series to export/20220111T054942, which is based on net-next/master at fe8152b38d3a (still the current HEAD). -- Mat Martineau Intel