lock warnings in dev_addr_lists test

From: Guenter Roeck
Date: Wed Feb 28 2024 - 14:45:17 EST


Hi,

when running the dev_addr_lists unit test with lock debugging enabled,
I always get the following lockdep warning.

[ 7.031327] ====================================
[ 7.031393] WARNING: kunit_try_catch/1886 still has locks held!
[ 7.031478] 6.8.0-rc6-00053-g0fec7343edb5-dirty #1 Tainted: G W N
[ 7.031728] ------------------------------------
[ 7.031816] 1 lock held by kunit_try_catch/1886:
[ 7.031896] #0: ffffffff8ed35008 (rtnl_mutex){+.+.}-{3:3}, at: dev_addr_test_init+0x6a/0x100

Instrumentation shows that dev_addr_test_exit() is called, but only
after the warning fires.

Is this a problem with kunit tests or a problem with this specific test ?

Thanks,
Guenter