linux-kernel - lock warnings in dev_addr

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

Date: Wed, 28 Feb 2024 11:45:00 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Jakub Kicinski <kuba@...nel.org>, Eric Dumazet <edumazet@...gle.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	Brendan Higgins <brendanhiggins@...gle.com>,
	David Gow <davidgow@...gle.com>, linux-kselftest@...r.kernel.org,
	kunit-dev@...glegroups.com
Subject: lock warnings in dev_addr_lists test

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