From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: linux-debuggers@vger.kernel.org
Subject: Re: Linux Kernel Debugging Tools Monthly Meeting on Wednesday, October 28th
Date: Wed, 28 Oct 2026 11:08:47 -0700 [thread overview]
Message-ID: <91f8d6dd-4475-498a-b512-412537e30f46@oracle.com> (raw)
In-Reply-To: <auEJ6HR8g3jNLIIa@os-N5J97HY9XQ>
Hi Omar,
On 10/27/26 1:30 PM, Omar Sandoval wrote:
> The next Linux Kernel Debugging Tools meeting is tomorrow, Wednesday,
> October 28th at 11:30 AM Pacific time. This meeting is a forum to
> discuss development of Linux kernel debugging tools like drgn, crash,
> and more.
>
> Note that the meeting will now be hosted on Google Meet.
>
> Here is the agenda so far:
>
> - Threat model for kernel debuggers. Philipp, Petr, and I had a
> discussion about this at LPC that would be nice to run by everyone
> else. I wrote a brief summary of my take in the drgn release notes:
> https://drgn.readthedocs.io/en/latest/release_highlights/0.3.0.html#hardening
> - drgn AI contribution guidelines.
Both very good topics, thanks.
One more topic I think would be good to touch base on is setting the
aarch64_insn_pac_mask for custom programs. I think the open question is
what would be a good API. The existing approach is new kwargs to the
Program() constructor (like vmcoreinfo). But I'm not sure if that's
appropriate to keep expanding.
https://github.com/osandov/drgn/issues/647
Thanks,
Stephen
> Please reply with anything else you'd like to add. As always, if you
> would like to attend, please email me offlist.
>
> Thanks!
> Omar
>
next prev parent reply other threads:[~2026-10-28 18:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 20:30 Linux Kernel Debugging Tools Monthly Meeting on Wednesday, October 28th Omar Sandoval
2026-10-28 18:08 ` Stephen Brennan [this message]
2026-10-28 19:21 ` Omar Sandoval
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=91f8d6dd-4475-498a-b512-412537e30f46@oracle.com \
--to=stephen.s.brennan@oracle.com \
--cc=linux-debuggers@vger.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