From: Petr Mladek <pmladek@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Petr Pavlu <petr.pavlu@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Alexei Starovoitov <ast@kernel.org>, Kees Cook <kees@kernel.org>,
Aaron Tomlin <atomlin@atomlin.com>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Daniel Gomez <da.gomez@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-modules@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/7] kallsyms: Prevent invalid access when showing module buildid
Date: Thu, 18 Dec 2025 10:09:15 +0100 [thread overview]
Message-ID: <aUPEuwRpMlAoy5SR@pathway.suse.cz> (raw)
In-Reply-To: <20251217130904.33163c243172324a5308efe9@linux-foundation.org>
On Wed 2025-12-17 13:09:04, Andrew Morton wrote:
> On Fri, 28 Nov 2025 14:59:13 +0100 Petr Mladek <pmladek@suse.com> wrote:
>
> > This patchset is cleaning up kallsyms code related to module buildid.
> > It is fixing an invalid access when printing backtraces, see [v1] for
> > more details:
> >
> > ...
> >
> > [v1] https://lore.kernel.org/r/20251105142319.1139183-1-pmladek@suse.com
> > [v2] https://lore.kernel.org/r/20251112142003.182062-1-pmladek@suse.com
> >
>
> It's best to avoid sending people off to the WWW to understand a
> patchset - better that the git history be self-contained.
I see. I'll do better next time.
> So when
> staging this for mm.git I scooped the relevant material from [1] and
> added it to your cover letter, as below. Looks OK?
It looks OK to me. Thanks for taking the patchset.
Best Regards,
Petr
prev parent reply other threads:[~2025-12-18 9:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 13:59 [PATCH v3 0/7] kallsyms: Prevent invalid access when showing module buildid Petr Mladek
2025-11-28 13:59 ` [PATCH v3 1/7] kallsyms: Clean up @namebuf initialization in kallsyms_lookup_buildid() Petr Mladek
2025-11-28 13:59 ` [PATCH v3 2/7] kallsyms: Clean up modname and modbuildid " Petr Mladek
2025-11-28 13:59 ` [PATCH v3 3/7] module: Add helper function for reading module_buildid() Petr Mladek
2025-11-28 13:59 ` [PATCH v3 4/7] kallsyms: Cleanup code for appending the module buildid Petr Mladek
2025-11-28 13:59 ` [PATCH v3 5/7] kallsyms/bpf: Rename __bpf_address_lookup() to bpf_address_lookup() Petr Mladek
2025-11-28 13:59 ` [PATCH v3 6/7] kallsyms/ftrace: Set module buildid in ftrace_mod_address_lookup() Petr Mladek
2025-11-28 13:59 ` [PATCH v3 7/7] kallsyms: Prevent module removal when printing module name and buildid Petr Mladek
2025-12-16 14:00 ` [PATCH v3 0/7] kallsyms: Prevent invalid access when showing module buildid Petr Mladek
2025-12-17 21:10 ` Andrew Morton
2025-12-17 21:09 ` Andrew Morton
2025-12-18 9:09 ` Petr Mladek [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=aUPEuwRpMlAoy5SR@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=atomlin@atomlin.com \
--cc=bpf@vger.kernel.org \
--cc=da.gomez@kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=rostedt@goodmis.org \
--cc=samitolvanen@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox