From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: Philipp Rudo <prudo@redhat.com>
Cc: Omar Sandoval <osandov@osandov.com>, <linux-debuggers@vger.kernel.org>
Subject: Unknown ORC entry type 5 on RHEL 9 kernel
Date: Thu, 04 Dec 2025 12:06:54 -0800 [thread overview]
Message-ID: <87h5u6j9k1.fsf@oracle.com> (raw)
Hi Philipp,
I wanted to let you know about an issue with drgn's stack unwinding on
the RHEL 9 kernel. It looks like that kernel backports some ORC changes,
without including a change Omar made (including an .orc_header section)
to help identify the ORC format version. I've included more details on
this drgn issue:
https://github.com/osandov/drgn/issues/578
The result is that drgn can't unwind stacks on the RHEL 9 kernel. I
think the best path forward would be to include the .orc_header patch:
b9f174c811e3a ("x86/unwind/orc: Add ELF section with ORC version identifier")
As it is, the RHEL 9 drgn can't unwind stacks on the RHEL 9 kernel,
which seems less than ideal.
Thanks,
Stephen
next reply other threads:[~2025-12-04 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 20:06 Stephen Brennan [this message]
2025-12-05 10:41 ` Unknown ORC entry type 5 on RHEL 9 kernel Philipp Rudo
2025-12-05 18:38 ` Stephen Brennan
2025-12-17 16:11 ` Philipp Rudo
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=87h5u6j9k1.fsf@oracle.com \
--to=stephen.s.brennan@oracle.com \
--cc=linux-debuggers@vger.kernel.org \
--cc=osandov@osandov.com \
--cc=prudo@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.