Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
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>,
	"Krzysztof Karas" <krzysztof.karas@intel.com>,
	"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 v14 0/9] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir
Date: Wed, 11 Jun 2025 07:15:24 -0700	[thread overview]
Message-ID: <20250611071524.45610986@kernel.org> (raw)
In-Reply-To: <20250610-reftrack-dbgfs-v14-0-efb532861428@kernel.org>

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

      parent reply	other threads:[~2025-06-11 14:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 14:59 [PATCH v14 0/9] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir Jeff Layton
2025-06-10 14:59 ` [PATCH v14 1/9] ref_tracker: don't use %pK in pr_ostream() output Jeff Layton
2025-06-10 14:59 ` [PATCH v14 2/9] ref_tracker: add a top level debugfs directory for ref_tracker Jeff Layton
2025-06-10 14:59 ` [PATCH v14 3/9] ref_tracker: have callers pass output function to pr_ostream() Jeff Layton
2025-06-11  9:42   ` Krzysztof Karas
2025-06-10 14:59 ` [PATCH v14 4/9] ref_tracker: add a static classname string to each ref_tracker_dir Jeff Layton
2025-06-11 10:32   ` Krzysztof Karas
2025-06-10 14:59 ` [PATCH v14 5/9] ref_tracker: allow pr_ostream() to print directly to a seq_file Jeff Layton
2025-06-11 10:52   ` Krzysztof Karas
2025-06-10 14:59 ` [PATCH v14 6/9] ref_tracker: automatically register a file in debugfs for a ref_tracker_dir Jeff Layton
2025-06-17  8:24   ` kernel test robot
2025-06-10 14:59 ` [PATCH v14 7/9] ref_tracker: add a way to create a symlink to the ref_tracker_dir debugfs file Jeff Layton
2025-06-10 14:59 ` [PATCH v14 8/9] net: add symlinks to ref_tracker_dir for netns Jeff Layton
2025-06-10 14:59 ` [PATCH v14 9/9] ref_tracker: eliminate the ref_tracker_dir name field Jeff Layton
2025-06-10 15:25 ` ✗ Fi.CI.CHECKPATCH: warning for ref_tracker: add ability to register a debugfs file for a ref_tracker_dir (rev10) Patchwork
2025-06-10 15:51 ` ✓ i915.CI.BAT: success " Patchwork
2025-06-10 17:50 ` ✓ i915.CI.Full: " Patchwork
2025-06-11 14:15 ` 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=20250611071524.45610986@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=krzysztof.karas@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