linux-kernel - Re: include: linux: slab: kmalloc_trace undefined when compiling drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 12 Nov 2022 17:11:27 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Ian Cowan <ian@...ux.cowan.aero>
Cc:     cl@...ux.com, penberg@...nel.org, rientjes@...gle.com,
        iamjoonsoo.kim@....com, roman.gushchin@...ux.dev,
        42.hyeyoo@...il.com, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: include: linux: slab: kmalloc_trace undefined when compiling
 drivers

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