From: Daniel Gomez <da.gomez@kernel.org>
To: "Sami Tolvanen" <samitolvanen@google.com>,
"Michal Suchánek" <msuchanek@suse.de>
Cc: linux-modules@vger.kernel.org,
Luis Chamberlain <mcgrof@kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gendwarfksyms: Fix build on 32-bit hosts
Date: Wed, 26 Nov 2025 20:59:55 +0100 [thread overview]
Message-ID: <9d9ca6f0-b4cc-4fef-9ca2-9cb754330581@kernel.org> (raw)
In-Reply-To: <CABCJKucc0bxLJ=b9rkiwWts6uA=ReLFr32K1OP9WH51D-hO4+A@mail.gmail.com>
On 25/11/2025 21.09, Sami Tolvanen wrote:
> On Tue, Nov 18, 2025 at 8:18 AM Michal Suchánek <msuchanek@suse.de> wrote:
>>
>> Hello,
>>
>> On Mon, Nov 17, 2025 at 08:38:07PM +0000, Sami Tolvanen wrote:
>>> We have interchangeably used unsigned long for some of the types
>>> defined in elfutils, assuming they're always 64-bit. This obviously
>>> fails when building gendwarfksyms on 32-bit hosts. Fix the types.
>>>
>>> Reported-by: Michal Suchánek <msuchanek@suse.de>
>>> Closes: https://lore.kernel.org/linux-modules/aRcxzPxtJblVSh1y@kitsune.suse.cz/
>>> Signed-off-by: Sami Tolvanen <samitolvanen@google.com>
>>> ---
>>> scripts/gendwarfksyms/dwarf.c | 4 +++-
>>> scripts/gendwarfksyms/symbols.c | 5 +++--
>>> 2 files changed, 6 insertions(+), 3 deletions(-)
>>
>> with this patch gendwarfksyms builds on 32bit x86 and Arm.
>>
>> Tested-by: Michal Suchánek <msuchanek@suse.de>
>
> Great, thanks for testing! Daniel, do you want to take this fix
> through the modules tree?
>
> Sami
Absolutely! Since we are at the end of the rc cycle, I'll merge this after
sending the current queued patches.
next prev parent reply other threads:[~2025-11-26 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 20:38 [PATCH] gendwarfksyms: Fix build on 32-bit hosts Sami Tolvanen
2025-11-18 16:18 ` Michal Suchánek
2025-11-25 20:09 ` Sami Tolvanen
2025-11-26 19:59 ` Daniel Gomez [this message]
2025-12-22 20:24 ` Sami Tolvanen
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=9d9ca6f0-b4cc-4fef-9ca2-9cb754330581@kernel.org \
--to=da.gomez@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=msuchanek@suse.de \
--cc=petr.pavlu@suse.com \
--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