linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "kernel test robot" <lkp@intel.com>, linuxppc-dev@lists.ozlabs.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Linux Memory Management List" <linux-mm@kvack.org>
Subject: Re: mm/slub.o: warning: objtool: ___slab_alloc.isra.111.part.112+0x4c0: can't find jump dest instruction at .text.___slab_alloc.isra.111.part.112+0x68c
Date: Mon, 07 Jul 2025 11:01:41 +0200	[thread overview]
Message-ID: <a38f2413-b13b-411d-88eb-7bde2852f9c2@app.fastmail.com> (raw)
In-Reply-To: <202507071557.SDU74U31-lkp@intel.com>

On Mon, Jul 7, 2025, at 09:56, kernel test robot wrote:
> commit: 4496e1c1354bd4837bcc1414f6e1a4d042857903 crash_dump, nvme: 
> select CONFIGFS_FS as built-in
...
>>> mm/slub.o: warning: objtool: ___slab_alloc.isra.111.part.112+0x4c0: can't find jump dest instruction at .text.___slab_alloc.isra.111.part.112+0x68c
>
> Kconfig warnings: (for reference only)
>    WARNING: unmet direct dependencies detected for HUGETLBFS
>    Depends on [n]: (X86 || SPARC64 || ARCH_SUPPORTS_HUGETLBFS [=y] || 
> BROKEN [=n]) && (SYSFS [=n] || SYSCTL [=n])
>    Selected by [y]:
>    - PPC_8xx [=y] && PPC32 [=y]
>

This is an existing bug on PPC_8xx that got exposed by my patch
but could already be triggered in randconfig builds without
CONFIG_SYSFS.

      Arnd


      reply	other threads:[~2025-07-07  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07  7:56 kernel test robot
2025-07-07  9:01 ` Arnd Bergmann [this message]

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=a38f2413-b13b-411d-88eb-7bde2852f9c2@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.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