[riteshharjani:kfence-hash-rfcv1 8/10] WARNING: modpost: vmlinux: section mismatch in reference: htab_bolt_mapping+0x5fc (section: .text) -> hash_kfence_add_slot (section: .init.text)

All of lore.kernel.org
 help / color / mirror / Atom feed

From: kernel test robot <lkp@intel.com>
To: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [riteshharjani:kfence-hash-rfcv1 8/10] WARNING: modpost: vmlinux: section mismatch in reference: htab_bolt_mapping+0x5fc (section: .text) -> hash_kfence_add_slot (section: .init.text)
Date: Fri, 26 Jul 2024 19:05:11 +0800	[thread overview]
Message-ID: <202407261926.HcVRPugo-lkp@intel.com> (raw)

tree:   https://github.com/riteshharjani/linux kfence-hash-rfcv1
head:   ab870b7bbabf70b4c07abf9163a509fbfaa79fe4
commit: a6abdbc7601fc172b2b07366f935771a2d02f284 [8/10] book3s64/hash: Add kfence functionality
config: powerpc64-randconfig-003-20240726 (https://download.01.org/0day-ci/archive/20240726/202407261926.HcVRPugo-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project ccae7b461be339e717d02f99ac857cf0bc7d17fc)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240726/202407261926.HcVRPugo-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202407261926.HcVRPugo-lkp@intel.com/

All warnings (new ones prefixed by >>, old ones prefixed by <<):

WARNING: modpost: missing MODULE_DESCRIPTION() in vmlinux.o
>> WARNING: modpost: vmlinux: section mismatch in reference: htab_bolt_mapping+0x5fc (section: .text) -> hash_kfence_add_slot (section: .init.text)

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-07-26 11:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202407261926.HcVRPugo-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ritesh.list@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.