linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Ian Cowan <ian@linux.cowan.aero>, cl@linux.com
Cc: 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 09:21:34 -0800	[thread overview]
Message-ID: <f83aca33-3a5f-97ac-625e-aa7c72bf60ba@infradead.org> (raw)
In-Reply-To: <Y2/Luovqgz8O+Kqa@rhino>

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:
> 
> 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


  reply	other threads:[~2022-11-12 17:21 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 [this message]
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
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=f83aca33-3a5f-97ac-625e-aa7c72bf60ba@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