linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Michal Marek <michal.lkml@markovi.net>
Subject: Re: Proper use for linking foo.o_shipped after 69ea912fda74 ("kbuild: remove unneeded link_multi_deps")?
Date: Wed, 6 May 2020 09:03:46 -0700	[thread overview]
Message-ID: <01279bfe-95a3-dbdb-3785-bd2d92dc4f95@gmail.com> (raw)
In-Reply-To: <CAK7LNAR5TsnUn2n2nDFHywQyqCT7si840yE2nyuxx70AYj+nDQ@mail.gmail.com>



On 5/6/2020 7:37 AM, Masahiro Yamada wrote:
> On Wed, May 6, 2020 at 1:45 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
>>
>> Hi Masahiro, Michal,
>>
>> While updating our systems from 4.9 to 5.4, we noticed that one of the
>> kernel modules that we build, which is done by linking an object that we
>> pre-compile out of Kbuild stopped working.
>>
>> I bisected it down to:
>>
>> commit 69ea912fda74a673d330d23595385e5b73e3a2b9 (refs/bisect/bad)
>> Author: Masahiro Yamada <yamada.masahiro@socionext.com>
>> Date:   Thu Oct 4 13:25:19 2018 +0900
>>
>>     kbuild: remove unneeded link_multi_deps
>>
>>     Since commit c8589d1e9e01 ("kbuild: handle multi-objs dependency
>>     appropriately"), $^ really represents all the prerequisite of the
>>     composite object being built.
>>
>>     Hence, $(filter %.o,$^) contains all the objects to link together,
>>     which is much simpler than link_multi_deps calculation.
>>
>>     Please note $(filter-out FORCE,$^) does not work here. When a single
>>     object module is turned into a multi object module, $^ will contain
>>     header files that were previously included for building the single
>>     object, and recorded in the .*.cmd file. To filter out such headers,
>>     $(filter %.o,$^) should be used here.
>>
>>     Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
>>
>> and the linker now fails with the following:
>>
>> mkdir -p /home/florian/dev/lkm/.tmp_versions ; rm -f
>> /home/florian/dev/lkm/.tmp_versions/*
>>
>>   WARNING: Symbol version dump ./Module.symvers
>>            is missing; modules will have no dependencies and modversions.
>>
>> make -f ./scripts/Makefile.build obj=/home/florian/dev/lkm
>> (cat /dev/null;   echo kernel//home/florian/dev/lkm/hello.ko;) >
>> /home/florian/dev/lkm/modules.order
>>   ld -m elf_x86_64  -z max-page-size=0x200000    -r -o
>> /home/florian/dev/lkm/hello.o
>> ld: no input files
>> make[1]: *** [scripts/Makefile.build:492: /home/florian/dev/lkm/hello.o]
>> Error 1
>> make: *** [Makefile:1530: _module_/home/florian/dev/lkm] Error 2
>>
>> and here are some steps to reproduce this:
>>
>> Kbuild:
>> obj-m   := hello.o
>> hello-y := test.o_shipped
>>
>> test.c can be a simple hello world, and you can compile it using a
>> standard Kbuild file first, and then move test.o as test.o_shipped.
> 
> 
> 
> Why don't you do like this?
> 
> obj-m   := hello.o
> hello-y := test.o

I tried it in the original environment where it failed, not my contrived
test case, and this did not work, as we really need test.o and
test.o_shipped to be separate objects, doing what you suggest results in
a circular dependency.

To me this is a regression, as it used to work and now it does not, thus
we should be fixing it, any idea about how we go about it without doing
a plain revert?

Thank you!
-- 
Florian

  reply	other threads:[~2020-05-06 16:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06  4:45 Proper use for linking foo.o_shipped after 69ea912fda74 ("kbuild: remove unneeded link_multi_deps")? Florian Fainelli
2020-05-06 14:37 ` Masahiro Yamada
2020-05-06 16:03   ` Florian Fainelli [this message]
2020-05-06 16:24     ` Masahiro Yamada
2020-05-06 22:10       ` Florian Fainelli

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=01279bfe-95a3-dbdb-3785-bd2d92dc4f95@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.lkml@markovi.net \
    /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;
as well as URLs for NNTP newsgroup(s).