[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250611071524.45610986@kernel.org>
Date: Wed, 11 Jun 2025 07:15:24 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jeff Layton <jlayton@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Simon Horman <horms@...nel.org>, Maarten Lankhorst
<maarten.lankhorst@...ux.intel.com>, Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>, David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>, Jani Nikula <jani.nikula@...ux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>, Rodrigo Vivi
<rodrigo.vivi@...el.com>, Tvrtko Ursulin <tursulin@...ulin.net>, Krzysztof
Karas <krzysztof.karas@...el.com>, Kuniyuki Iwashima <kuniyu@...zon.com>,
Qasim Ijaz <qasdev00@...il.com>, Nathan Chancellor <nathan@...nel.org>,
Andrew Lunn <andrew@...n.ch>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, dri-devel@...ts.freedesktop.org,
intel-gfx@...ts.freedesktop.org, Thomas Weißschuh
<thomas.weissschuh@...utronix.de>
Subject: Re: [PATCH v14 0/9] ref_tracker: add ability to register a debugfs
file for a ref_tracker_dir
On Tue, 10 Jun 2025 10:59:20 -0400 Jeff Layton wrote:
> For those just joining in, this series adds a new top-level
> "ref_tracker" debugfs directory, and has each ref_tracker_dir register a
> file in there as part of its initialization. It also adds the ability to
> register a symlink with a more human-usable name that points to the
> file, and does some general cleanup of how the ref_tracker object names
> are handled.
Still has the lockdep problem. Please triple check that it's fixed
before you post next version, the number of warnings this series
generates is quite burdensome for our CI.
[ 440.139336][ C1] ================================
[ 440.139684][ C1] WARNING: inconsistent lock state
[ 440.140019][ C1] 6.15.0-virtme #1 Not tainted
[ 440.140360][ C1] --------------------------------
[ 440.140705][ C1] inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
[ 440.141124][ C1] ksoftirqd/1/22 [HC0[0]:SC1[1]:HE1:SE0] takes:
[ 440.141541][ C1] ffffffffad243218 (&xa->xa_lock#8){+.?.}-{3:3}, at: xa_set_mark+0x73/0x120
[ 440.142146][ C1] {SOFTIRQ-ON-W} state was registered at:
[ 440.142485][ C1] __lock_acquire+0x20b/0x7e0
[ 440.142832][ C1] lock_acquire.part.0+0xb6/0x240
[ 440.143181][ C1] _raw_spin_lock+0x33/0x40
[ 440.143521][ C1] xa_store+0x1c/0x50
[ 440.143784][ C1] ref_tracker_dir_debugfs+0x168/0x1b0
[ 440.144137][ C1] init_net_debugfs+0x15/0x70
[ 440.144480][ C1] do_one_initcall+0x8c/0x1e0
[ 440.144845][ C1] do_initcalls+0x176/0x280
[ 440.145184][ C1] kernel_init_freeable+0x22d/0x300
[ 440.145530][ C1] kernel_init+0x20/0x200
[ 440.145871][ C1] ret_from_fork+0x240/0x320
[ 440.146205][ C1] ret_from_fork_asm+0x1a/0x30
[ 440.146545][ C1] irq event stamp: 5141102
[ 440.146886][ C1] hardirqs last enabled at (5141102): [<ffffffffa96fa4ed>] _raw_spin_unlock_irqrestore+0x5d/0x80
[ 440.147613][ C1] hardirqs last disabled at (5141101): [<ffffffffa96fa1cb>] _raw_spin_lock_irqsave+0x5b/0x60
[ 440.148283][ C1] softirqs last enabled at (5139838): [<ffffffffa6c8ef18>] handle_softirqs+0x358/0x620
[ 440.148883][ C1] softirqs last disabled at (5139843): [<ffffffffa6c8f41f>] run_ksoftirqd+0x3f/0x70
https://netdev-3.bots.linux.dev/vmksft-mptcp-dbg/results/160722/1-mptcp-join-sh/stderr
https://netdev-3.bots.linux.dev/vmksft-mptcp-dbg/results/160722/vm-crash-thr0-0
--
pw-bot: cr
Powered by blists - more mailing lists