From: Jakub Kicinski <kuba@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Kuniyuki Iwashima" <kuniyu@amazon.com>,
"Qasim Ijaz" <qasdev00@gmail.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Andrew Lunn" <andrew@lunn.ch>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: Re: [PATCH v12 00/10] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir
Date: Thu, 29 May 2025 16:24:47 -0700 [thread overview]
Message-ID: <20250529162447.30c4ca85@kernel.org> (raw)
In-Reply-To: <20250529-reftrack-dbgfs-v12-0-11b93c0c0b6e@kernel.org>
On Thu, 29 May 2025 11:20:36 -0400 Jeff Layton wrote:
> Sorry for the reposting, but this makes things easier with automated CI.
>
> This posting just drops the pr_warn() calls from the new functions. We
> were still seeing some warnings during (expected) times that debugfs
> file creation would fail. debugfs already throws warnings when these
> things fail unexpectedly, so these warnings are unwanted when dentry
> creation fails before debugfs is up.
Hm, so FWIW we hit a lockdep issue now
raw:
https://netdev-3.bots.linux.dev/vmksft-tcp-ao-dbg/results/142540/4-connect-deny-ipv6/stderr
decoded:
https://netdev-3.bots.linux.dev/vmksft-tcp-ao-dbg/results/142540/vm-crash-thr0-10
I suspect this may just be "merge window fun", since we forwarded our
trees to Linus's since your v11?
[ 14.281410][ C0] inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
[ 14.281692][ C0] swapper/0/0 [HC0[0]:SC1[1]:HE1:SE0] takes:
[ 14.281974][ C0] ffffffff9e1c5af8 (pin_fs_lock){+.?.}-{3:3}, at: simple_pin_fs+0x24/0x150
[ 14.282373][ C0] {SOFTIRQ-ON-W} state was registered at:
[ 14.282614][ C0] __lock_acquire+0x20b/0x7e0
[ 14.282849][ C0] lock_acquire.part.0+0xb6/0x240
[ 14.283072][ C0] _raw_spin_lock+0x33/0x40
[ 14.283298][ C0] simple_pin_fs+0x24/0x150
[ 14.283524][ C0] start_creating.part.0+0x52/0x310
[ 14.283752][ C0] debugfs_create_dir+0x6a/0x540
[ 14.283977][ C0] component_debug_init+0x17/0x30
[ 14.284206][ C0] do_one_initcall+0x8f/0x1e0
[ 14.284451][ C0] do_initcalls+0x176/0x280
[ 14.284679][ C0] kernel_init_freeable+0x22d/0x300
[ 14.284907][ C0] kernel_init+0x20/0x200
[ 14.285131][ C0] ret_from_fork+0x240/0x320
[ 14.285359][ C0] ret_from_fork_asm+0x1a/0x30
[ 14.285580][ C0] irq event stamp: 410868
[ 14.285750][ C0] hardirqs last enabled at (410868): [<ffffffff9cfc332d>] _raw_spin_unlock_irqrestore+0x5d/0x80
[ 14.286200][ C0] hardirqs last disabled at (410867): [<ffffffff9cfc300b>] _raw_spin_lock_irqsave+0x5b/0x60
[ 14.286653][ C0] softirqs last enabled at (409604): [<ffffffff9a6877a8>] handle_softirqs+0x358/0x620
[ 14.287061][ C0] softirqs last disabled at (409635): [<ffffffff9a687bfa>] __irq_exit_rcu+0xfa/0x160
prev parent reply other threads:[~2025-05-29 23:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 15:20 [PATCH v12 00/10] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir Jeff Layton
2025-05-29 15:20 ` [PATCH v12 01/10] i915: only initialize struct ref_tracker_dir once Jeff Layton
2025-05-30 11:01 ` Krzysztof Karas
2025-05-30 11:39 ` Jeff Layton
2025-05-29 15:20 ` [PATCH v12 02/10] ref_tracker: don't use %pK in pr_ostream() output Jeff Layton
2025-05-30 11:03 ` Krzysztof Karas
2025-05-29 15:20 ` [PATCH v12 03/10] ref_tracker: add a top level debugfs directory for ref_tracker Jeff Layton
2025-05-30 11:05 ` Krzysztof Karas
2025-06-04 9:12 ` Jani Nikula
2025-06-09 18:10 ` Jeff Layton
2025-05-29 15:20 ` [PATCH v12 04/10] ref_tracker: have callers pass output function to pr_ostream() Jeff Layton
2025-05-30 11:13 ` Krzysztof Karas
2025-05-30 11:47 ` Jeff Layton
2025-05-29 15:20 ` [PATCH v12 05/10] ref_tracker: add a static classname string to each ref_tracker_dir Jeff Layton
2025-05-29 15:20 ` [PATCH v12 06/10] ref_tracker: allow pr_ostream() to print directly to a seq_file Jeff Layton
2025-05-29 15:20 ` [PATCH v12 07/10] ref_tracker: automatically register a file in debugfs for a ref_tracker_dir Jeff Layton
2025-05-29 15:20 ` [PATCH v12 08/10] ref_tracker: add a way to create a symlink to the ref_tracker_dir debugfs file Jeff Layton
2025-05-29 15:20 ` [PATCH v12 09/10] net: add symlinks to ref_tracker_dir for netns Jeff Layton
2025-05-29 15:20 ` [PATCH v12 10/10] ref_tracker: eliminate the ref_tracker_dir name field Jeff Layton
2025-05-29 23:24 ` Jakub Kicinski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250529162447.30c4ca85@kernel.org \
--to=kuba@kernel.org \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jlayton@kernel.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qasdev00@gmail.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=thomas.weissschuh@linutronix.de \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).