From: Randy Dunlap <rdunlap@infradead.org>
To: Ian Cowan <ian@linux.cowan.aero>
Cc: cl@linux.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, roman.gushchin@linux.dev,
42.hyeyoo@gmail.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: include: linux: slab: kmalloc_trace undefined when compiling drivers
Date: Sat, 12 Nov 2022 17:11:27 -0800 [thread overview]
Message-ID: <abdb1b8d-859d-669b-6bbf-604febb643b2@infradead.org> (raw)
In-Reply-To: <Y3A9waTkehESUyn+@rhino>
On 11/12/22 16:43, Ian Cowan wrote:
> On Sat, Nov 12, 2022 at 04:34:18PM -0800, Randy Dunlap wrote:
>>
>>
>> On 11/12/22 13:59, Ian Cowan wrote:
>>> On Sat, Nov 12, 2022 at 09:21:34AM -0800, Randy Dunlap wrote:
>>>> Hi--
>>>>
>>>> On 11/12/22 08:37, Ian Cowan wrote:
>>>>> When compiling drivers (speficially drivers/pci/hotplug), I am receiving
>>>>> the following modpost error for both `kmalloc_trace` and
>>>>> `kmalloc_node_trace` on the staging/staging-next branch:
>>>>>
>>
>> Ian, what do you mean by "on the staging/staging-next branch"?
>>
>> What kernel version are you trying to build?
>>
>> The .config that you sent is for v6.1.0-rc1.
>
> I am building from the staging repository (gregkh/staging) and my
> working branch when building is staging-next. So I am trying to build
> from staging and not a particular version. I have also run `make modules_prepare`
> and updated the .config per that script. However, when I do build
> v6.1.0-rc1 from the main repository (torvalds/linux), I run into the same problem.
Have you built the entire kernel already and then you are trying to build
only drivers/pci/hotplug?
If I build *only* drivers/pci/hotplug, I do get undefined symbols:
WARNING: modpost: "strcmp" [drivers/pci/hotplug/acpiphp_ibm.ko] undefined!
WARNING: modpost: "kfree" [drivers/pci/hotplug/acpiphp_ibm.ko] undefined!
WARNING: modpost: "pci_slots_kset" [drivers/pci/hotplug/acpiphp_ibm.ko] undefined!
WARNING: modpost: "acpiphp_unregister_attention" [drivers/pci/hotplug/acpiphp_ibm.ko] undefined!
WARNING: modpost: "acpi_remove_notify_handler" [drivers/pci/hotplug/acpiphp_ibm.ko] undefined!
WARNING: modpost: "sysfs_remove_bin_file" [drivers/pci/hotplug/acpiphp_ibm.ko] undefined!
WARNING: modpost: "acpi_evaluate_object" [drivers/pci/hotplug/acpiphp_ibm.ko] undefined!
WARNING: modpost: "__kmalloc" [drivers/pci/hotplug/acpiphp_ibm.ko] undefined!
WARNING: modpost: "memcpy" [drivers/pci/hotplug/acpiphp_ibm.ko] undefined!
WARNING: modpost: "acpi_walk_namespace" [drivers/pci/hotplug/acpiphp_ibm.ko] undefined!
WARNING: modpost: suppressed 14 unresolved symbol warnings because there were too many)
but that's understandable since the object files that would contain those symbols
have not been built yet.
--
~Randy
next prev parent reply other threads:[~2022-11-13 1:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 16:37 Ian Cowan
2022-11-12 17:21 ` Randy Dunlap
2022-11-12 21:59 ` Ian Cowan
2022-11-13 0:34 ` Randy Dunlap
2022-11-13 0:43 ` Ian Cowan
2022-11-13 1:11 ` Randy Dunlap [this message]
2022-11-13 1:21 ` Ian Cowan
2022-11-14 8:59 ` Hyeonggon Yoo
2022-11-14 12:39 ` Ian Cowan
2022-11-14 16:56 ` Vlastimil Babka
2022-11-14 21:28 ` Ian Cowan
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=abdb1b8d-859d-669b-6bbf-604febb643b2@infradead.org \
--to=rdunlap@infradead.org \
--cc=42.hyeyoo@gmail.com \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=ian@linux.cowan.aero \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
/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