From: Greg Ungerer <gerg@kernel.org>
To: Masahiro Yamada <masahiroy@kernel.org>, linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Jack Brennen <jbrennen@google.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicolas Schier <nicolas@fjasle.eu>
Subject: Re: [PATCH 0/7] modpost: fix modpost errors for m68k-uclinux-gcc
Date: Fri, 3 Nov 2023 01:00:33 +1000 [thread overview]
Message-ID: <868f4920-190d-4917-ae4e-bd4cbb6de98f@kernel.org> (raw)
In-Reply-To: <20231101150404.754108-1-masahiroy@kernel.org>
Hi Masahiro,
On 2/11/23 01:03, Masahiro Yamada wrote:
> Greg Ungerer reports building with m68k-uclinux-gcc toolchain is broken:
> https://lore.kernel.org/linux-kbuild/CAK7LNASQ_W5Yva5a4Xx8E2EYi-tN7x3OHgMFhK+93W+BiX1=9Q@mail.gmail.com/T/#m6ff0364f9ca8483c9f6d162619e5005833d1e887
>
> Usually, we do not need to search for export symbols in the .symtab
> section, but m68k-uclinux-gcc seems to be an exceptional case.
> I do not know what makes it different from other toolchains.
> Also, I do not know there exist other toolchains that work like that.
>
> This series extends the symsearch feature in case we need to explicitly
> search for export symbols.
>
> Then, the last patch fixes the issue.
>
> This series should be applicable for linux-next.
>
> This series is too late for the current merge window, but I'd like
> to fix the issue somehow by the next merge window.
Thanks for looking into this.
I can confirm this series fixes it for me (using linux-next).
Tested-by: Greg Ungerer <gerg@kernel.org>
Regards
Greg
>
>
> Masahiro Yamada (7):
> modpost: move sym_name() to modpost.h
> modpost: add const qualifier to syminfo table
> modpost: add table_size local variable to symsearch_find_nearest()
> modpost: introduce a filtering feature to symsearch
> modpost: prefer global symbols in symsearch_find_nearest()
> modpost: add symsearch_find_with_name() helper function
> modpost: look up the correct symbol in check_export_symbol()
>
> scripts/mod/modpost.c | 39 ++++----
> scripts/mod/modpost.h | 12 +++
> scripts/mod/symsearch.c | 205 ++++++++++++++++++++++++++++------------
> 3 files changed, 180 insertions(+), 76 deletions(-)
>
prev parent reply other threads:[~2023-11-02 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 15:03 [PATCH 0/7] modpost: fix modpost errors for m68k-uclinux-gcc Masahiro Yamada
2023-11-01 15:03 ` [PATCH 1/7] modpost: move sym_name() to modpost.h Masahiro Yamada
2023-11-01 15:03 ` [PATCH 2/7] modpost: add const qualifier to syminfo table Masahiro Yamada
2023-11-01 15:04 ` [PATCH 3/7] modpost: add table_size local variable to symsearch_find_nearest() Masahiro Yamada
2023-11-01 15:04 ` [PATCH 4/7] modpost: introduce a filtering feature to symsearch Masahiro Yamada
2023-11-01 15:04 ` [PATCH 5/7] modpost: prefer global symbols in symsearch_find_nearest() Masahiro Yamada
2023-11-01 15:04 ` [PATCH 6/7] modpost: add symsearch_find_with_name() helper function Masahiro Yamada
2023-11-01 15:04 ` [PATCH 7/7] modpost: look up the correct symbol in check_export_symbol() Masahiro Yamada
2023-11-02 15:00 ` Greg Ungerer [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=868f4920-190d-4917-ae4e-bd4cbb6de98f@kernel.org \
--to=gerg@kernel.org \
--cc=jbrennen@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
/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