From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kbuild-all@lists.01.org
Subject: Re: [stable:linux-5.4.y 5541/6083] ERROR: "__memcat_p" [drivers/hwtracing/stm/stm_core.ko] undefined!
Date: Tue, 04 May 2021 06:42:57 +0200 [thread overview]
Message-ID: <YJDQ0ePGHxmcB7dX@kroah.com> (raw)
In-Reply-To: <CAK8P3a3KLasm-CdcM3HCP6EZO1Vr0ay17jw7zSy0btqPr32WRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
On Mon, May 03, 2021 at 09:16:42PM +0200, Arnd Bergmann wrote:
> On Mon, May 3, 2021 at 7:00 PM 'Nick Desaulniers' via Clang Built
> Linux <clang-built-linux@googlegroups.com> wrote:
> > > > >> ERROR: "__memcat_p" [drivers/hwtracing/stm/stm_core.ko] undefined!
> > >
> > > I'm fairly sure this is unrelated to my patch, but I don't see what
> > > happened here.
> >
> > It's unrelated to your patch. It was fixed in 5.7 by
> > 7273ad2b08f8ac9563579d16a3cf528857b26f49 and a few other dependencies
> > according to https://github.com/ClangBuiltLinux/linux/issues/515.
> >
>
> Ah right, the big hammer.
>
> Greg, not sure what we want to do here. Backporting
>
> 7273ad2b08f8 ("kbuild: link lib-y objects to vmlinux forcibly when
> CONFIG_MODULES=y")
>
> to v5.4 and earlier would be an easy workaround, but it has the potential
> of adding extra bloat to the kernel image since it links in all other
> library objects as well.
I've lost the thread here, but what _real_ problem is happening here
that doing the above is required?
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org,
clang-built-linux <clang-built-linux@googlegroups.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Sasha Levin <sashal@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Masahiro Yamada <masahiroy@kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [stable:linux-5.4.y 5541/6083] ERROR: "__memcat_p" [drivers/hwtracing/stm/stm_core.ko] undefined!
Date: Tue, 4 May 2021 06:42:57 +0200 [thread overview]
Message-ID: <YJDQ0ePGHxmcB7dX@kroah.com> (raw)
In-Reply-To: <CAK8P3a3KLasm-CdcM3HCP6EZO1Vr0ay17jw7zSy0btqPr32WRg@mail.gmail.com>
On Mon, May 03, 2021 at 09:16:42PM +0200, Arnd Bergmann wrote:
> On Mon, May 3, 2021 at 7:00 PM 'Nick Desaulniers' via Clang Built
> Linux <clang-built-linux@googlegroups.com> wrote:
> > > > >> ERROR: "__memcat_p" [drivers/hwtracing/stm/stm_core.ko] undefined!
> > >
> > > I'm fairly sure this is unrelated to my patch, but I don't see what
> > > happened here.
> >
> > It's unrelated to your patch. It was fixed in 5.7 by
> > 7273ad2b08f8ac9563579d16a3cf528857b26f49 and a few other dependencies
> > according to https://github.com/ClangBuiltLinux/linux/issues/515.
> >
>
> Ah right, the big hammer.
>
> Greg, not sure what we want to do here. Backporting
>
> 7273ad2b08f8 ("kbuild: link lib-y objects to vmlinux forcibly when
> CONFIG_MODULES=y")
>
> to v5.4 and earlier would be an easy workaround, but it has the potential
> of adding extra bloat to the kernel image since it links in all other
> library objects as well.
I've lost the thread here, but what _real_ problem is happening here
that doing the above is required?
thanks,
greg k-h
next prev parent reply other threads:[~2021-05-04 4:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 19:28 [stable:linux-5.4.y 5541/6083] ERROR: "__memcat_p" [drivers/hwtracing/stm/stm_core.ko] undefined! kernel test robot
2021-05-02 19:28 ` kernel test robot
2021-05-03 12:41 ` Arnd Bergmann
2021-05-03 12:41 ` Arnd Bergmann
2021-05-03 17:00 ` Nick Desaulniers
2021-05-03 17:00 ` Nick Desaulniers
2021-05-03 19:16 ` Arnd Bergmann
2021-05-03 19:16 ` Arnd Bergmann
2021-05-04 4:42 ` Greg Kroah-Hartman [this message]
2021-05-04 4:42 ` Greg Kroah-Hartman
2021-05-04 7:41 ` Arnd Bergmann
2021-05-04 7:41 ` Arnd Bergmann
2021-05-04 8:25 ` Greg Kroah-Hartman
2021-05-04 8:25 ` Greg Kroah-Hartman
2021-05-04 10:46 ` Arnd Bergmann
2021-05-04 10:46 ` Arnd Bergmann
2021-05-04 14:16 ` Greg Kroah-Hartman
2021-05-04 14:16 ` Greg Kroah-Hartman
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=YJDQ0ePGHxmcB7dX@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.