On Fri, Nov 7, 2025 at 5:15 AM Petr Mladek <[email protected]> wrote: > > On Wed 2025-11-05 14:59:53, [email protected] wrote: > > > diff --git a/kernel/kallsyms.c b/kernel/kallsyms.c > > > index 1e7635864..9455e3bb0 100644 > > > --- a/kernel/kallsyms.c > > > +++ b/kernel/kallsyms.c > > > @@ -423,6 +423,37 @@ int lookup_symbol_name(unsigned long addr, char > > > *symname) > > > return lookup_module_symbol_name(addr, symname); > > > } > > > > > > +#ifdef CONFIG_STACKTRACE_BUILD_ID > > > + > > > +static int append_buildid(char *buffer, const char *modname, > > > + const unsigned char *buildid) > > > +{ > > > + if (!modname) > > > + return 0; > > > + > > > + if (!buildid) { > > > + pr_warn_once("Undefined buildid for the module %s\n", > > > modname); > > > + return 0; > > > + } > > > > When ftrace_mod_address_lookup() succeeds in kallsyms_lookup_buildid(), > > it sets *modname but doesn't initialize *modbuildid. This leaves the > > buildid variable uninitialized when __sprint_symbol() calls > > append_buildid(). > > Just for record. This is a great analyze. This patchset is fixing > this bug in a later patch. ;-)
Currently AI analyses one patch at a time and comments on what it understands the way humans would do if they read and comment as they go. Teaching AI to understand the whole series is on todo list. Chris may comment on how feasible that is.
