[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250307111407.0073ff75@gandalf.local.home>
Date: Fri, 7 Mar 2025 11:14:07 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Kris Van Hees <kris.van.hees@...cle.com>
Cc: Masahiro Yamada <masahiroy@...nel.org>, linux-kernel@...r.kernel.org,
linux-kbuild@...r.kernel.org, linux-modules@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, Nick Alcock <nick.alcock@...cle.com>,
Alan Maguire <alan.maguire@...cle.com>, Sam James <sam@...too.org>, Luis
Chamberlain <mcgrof@...nel.org>, Masami Hiramatsu <mhiramat@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>, Jiri Olsa <olsajiri@...il.com>,
Elena Zannoni <elena.zannoni@...cle.com>, Daniel Gomez
<da.gomez@...sung.com>, Jack Vogel <jack.vogel@...cle.com>
Subject: Re: [PATCH] kbuild: exclude .rodata.(cst|str)* when building ranges
On Wed, 5 Mar 2025 14:27:58 -0500
Kris Van Hees <kris.van.hees@...cle.com> wrote:
> The .rodata.(cst|str)* sections are often resized during the final
> linking and since these sections do not cover actual symbols there is
> no need to include them in the modules.builtin.ranges data.
>
> When these sections were included in processing and resizing occurred,
> modules were reported with ranges that extended beyond their true end,
> causing subsequent symbols (in address order) to be associated with
> the wrong module.
If that's the case, shouldn't this be considered a fix, and include a fixes
tag as well as Cc stable?
-- Steve
>
> Signed-off-by: Kris Van Hees <kris.van.hees@...cle.com>
> Reviewed-by: Jack Vogel <jack.vogel@...cle.com>
> ---
Powered by blists - more mailing lists