[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1df133ef-d5e9-f323-7c67-fc9ffed04274@infradead.org>
Date: Sat, 12 Nov 2022 16:34:18 -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 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.
>>> ERROR: modpost: "kmalloc_trace" [drivers/pci/hotplug/acpiphp_ibm.ko] undefined!
>>>
>>> This only occurs when I have 'CONFIG_TRACING=y' in my config, and I
>>> have traced it down to the slab header where the kmalloc_trace is
>>> defined. It appears that when CONFIG_TRACING is set, the kmalloc_trace
>>> and kmalloc_node_trace do not get defined by the compiler. I do not have
>>> enough context in this area of the code base to propose a fix or to even
>>> know if maybe it's a local compiling issue for myself. It looks like
>>> there are a few recent commits from August that did some refactoring in this header,
>>> and when compiling prior to that refactoring I am able to compile the
>>> specified drivers without error.
>>>
>>> I will mention that I am using Red Hat gcc version 12.2.1 and make version
>>> 4.3 and am on Fedora.
>> Please post a full failing kernel .config file for this.
>> Thanks.
>>
>> --
>> ~Randy
>>
> Below is my .config file. This is pretty much a default Fedora .config
> (copied from my system) with possibly a few additions to make sure the
> modules I needed to compile did compile. I was compiling using the
> command: `make M=drivers/pci/hotplug`.
Sorry, I cannot reproduce the problem.
Hopefully someone else has some ideas.
--
~Randy
Powered by blists - more mailing lists