From: Illia Ostapyshyn <illia@yshyn.com>
To: linux-kernel@vger.kernel.org
Cc: Hao Li <hao.li@linux.dev>, Harry Yoo <harry@kernel.org>,
"Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
Illia Ostapyshyn <illia@yshyn.com>,
Andrew Morton <akpm@linux-foundation.org>,
Seongjun Hong <hsj0512@snu.ac.kr>,
Kieran Bingham <kbingham@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Florian Fainelli <florian.fainelli@broadcom.com>
Subject: [PATCH 0/2] Fixes related to lx-slabinfo, lx-slabtrace
Date: Mon, 27 Apr 2026 16:24:46 +0200 [thread overview]
Message-ID: <20260427142448.666117-1-illia@yshyn.com> (raw)
Hi all,
calling slab-related commands in gdb scripts currently fails because
of two reasons. Firstly, x86 mm page ops try to cast symbols without
type information to int, which causes an exception. Secondly, struct
kmem_cache was changed in commit 55f8b4518d14b743 ("scripts/gdb:
implement x86_page_ops in mm.py") to factor out per-node data into a
separate struct, which the gdb scripts do not reflect yet.
These two patches fix these issues.
Illia Ostapyshyn (2):
scripts/gdb: mm: Cast untyped symbols in x86_page_ops
scripts/gdb: slab: Update field names of struct kmem_cache
scripts/gdb/linux/mm.py | 6 +++---
scripts/gdb/linux/slab.py | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
base-commit: 254f49634ee16a731174d2ae34bc50bd5f45e731
--
2.51.2
next reply other threads:[~2026-04-27 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 14:24 Illia Ostapyshyn [this message]
2026-04-27 14:24 ` [PATCH 1/2] scripts/gdb: mm: Cast untyped symbols in x86_page_ops Illia Ostapyshyn
2026-04-27 14:24 ` [PATCH 2/2] scripts/gdb: slab: Update field names of struct kmem_cache Illia Ostapyshyn
2026-04-28 6:04 ` Harry Yoo (Oracle)
2026-04-28 8:20 ` Vlastimil Babka (SUSE)
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=20260427142448.666117-1-illia@yshyn.com \
--to=illia@yshyn.com \
--cc=akpm@linux-foundation.org \
--cc=florian.fainelli@broadcom.com \
--cc=hao.li@linux.dev \
--cc=harry@kernel.org \
--cc=hsj0512@snu.ac.kr \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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