Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Caleb Kan <calebkan1106@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	 kasan-dev@googlegroups.com, Vlastimil Babka <vbabka@kernel.org>,
	 Alexander Potapenko <glider@google.com>,
	Marco Elver <elver@google.com>,
	 Dmitry Vyukov <dvyukov@google.com>,
	Andrey Konovalov <andreyknvl@gmail.com>,
	 Oscar Salvador <osalvador@suse.de>,
	Caleb Kan <ckan@cloudflare.com>,
	 kernel-team@cloudflare.com
Subject: [PATCH RFC 7/9] drm/locking: preserve deadlock diagnostics for trie-backed stacks
Date: Mon, 17 Aug 2026 13:42:47 +0100	[thread overview]
Message-ID: <20260817-stackdepot-trie-v1-7-53870ca1651b@cloudflare.com> (raw)
In-Reply-To: <20260817-stackdepot-trie-v1-0-53870ca1651b@cloudflare.com>

From: Caleb Kan <ckan@cloudflare.com>

When a modeset lock acquisition returns -EDEADLK, DRM saves the call chain
and prints it if the caller later attempts another lock or drops its locks
without first calling drm_modeset_backoff(). This diagnostic currently
fetches the saved stack through stack_depot_fetch().

Persistent stack depot saves can now return trie-backed handles, while
stack_depot_fetch() remains limited to hash-backed records. Use
stack_depot_snprint() to format either backend. Preserve the PAGE_SIZE
buffer, two-space indentation, warning, and backtrace.

Signed-off-by: Caleb Kan <ckan@cloudflare.com>
---
 drivers/gpu/drm/drm_modeset_lock.c | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/drivers/gpu/drm/drm_modeset_lock.c b/drivers/gpu/drm/drm_modeset_lock.c
index 2c806b0146d6..a2ddb02b2aea 100644
--- a/drivers/gpu/drm/drm_modeset_lock.c
+++ b/drivers/gpu/drm/drm_modeset_lock.c
@@ -94,16 +94,13 @@ static noinline depot_stack_handle_t __drm_stack_depot_save(void)
 static void __drm_stack_depot_print(depot_stack_handle_t stack_depot)
 {
 	struct drm_printer p = drm_dbg_printer(NULL, DRM_UT_KMS, "drm_modeset_lock");
-	unsigned long *entries;
-	unsigned int nr_entries;
 	char *buf;
 
 	buf = kmalloc(PAGE_SIZE, GFP_NOWAIT | __GFP_NOWARN);
 	if (!buf)
 		return;
 
-	nr_entries = stack_depot_fetch(stack_depot, &entries);
-	stack_trace_snprint(buf, PAGE_SIZE, entries, nr_entries, 2);
+	stack_depot_snprint(stack_depot, buf, PAGE_SIZE, 2);
 
 	drm_printf(&p, "attempting to lock a contended lock without backoff:\n%s", buf);
 

-- 
Git-155)



  parent reply	other threads:[~2026-08-17 12:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 12:42 [PATCH RFC 0/9] Path-compressed trie storage for persistent stack depot records Caleb Kan
2026-08-17 12:42 ` [PATCH RFC 1/9] stackdepot: share persistent stack prefixes with trie storage Caleb Kan
2026-08-17 12:42 ` [PATCH RFC 2/9] stackdepot: add KUnit tests for " Caleb Kan
2026-08-17 12:42 ` [PATCH RFC 3/9] mm/page_owner: preserve accounting with countable stack depot records Caleb Kan
2026-08-17 12:42 ` [PATCH RFC 4/9] mm/kmemleak: print trie-backed stack depot traces Caleb Kan
2026-08-17 12:42 ` [PATCH RFC 5/9] kmsan: report " Caleb Kan
2026-08-17 12:42 ` [PATCH RFC 6/9] mm/slub: materialize " Caleb Kan
2026-08-17 12:42 ` Caleb Kan [this message]
2026-08-17 12:42 ` [PATCH RFC 8/9] scripts/gdb: reject trie-backed stack depot handles Caleb Kan
2026-08-17 12:42 ` [PATCH RFC 9/9] stackdepot: add boot-time activation for trie storage Caleb Kan
2026-08-18 13:17 ` [PATCH RFC 0/9] Path-compressed trie storage for persistent stack depot records Marco Elver
2026-08-18 16:28   ` Caleb Kan

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=20260817-stackdepot-trie-v1-7-53870ca1651b@cloudflare.com \
    --to=calebkan1106@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@gmail.com \
    --cc=ckan@cloudflare.com \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=glider@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=kernel-team@cloudflare.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=osalvador@suse.de \
    --cc=vbabka@kernel.org \
    /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