linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: SeongJae Park <sj@kernel.org>, Honggyu Kim <honggyu.kim@sk.com>,
	oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 7416/10451] WARNING: modpost: vmlinux: section mismatch in reference: svc_xprt_create_from_sa+0x6e (section: .text) -> .L96 (section: .init.text)
Date: Wed, 10 Jul 2024 17:32:51 -0700	[thread overview]
Message-ID: <20240711003251.161484-1-sj@kernel.org> (raw)
In-Reply-To: <202407090506.BxtnYHgZ-lkp@intel.com>

Hello,

On Tue, 9 Jul 2024 05:52:19 +0800 kernel test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   0b58e108042b0ed28a71cd7edf5175999955b233
> commit: c3bf782bb0fffebcc4e467033cf6bf5e5e1b0784 [7416/10451] mm: make alloc_demote_folio externally invokable for migration
> config: riscv-randconfig-r033-20230517 (https://download.01.org/0day-ci/archive/20240709/202407090506.BxtnYHgZ-lkp@intel.com/config)
> compiler: riscv32-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240709/202407090506.BxtnYHgZ-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/202407090506.BxtnYHgZ-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>, old ones prefixed by <<):
> 
[...]
> >> WARNING: modpost: vmlinux: section mismatch in reference: svc_xprt_create_from_sa+0x6e (section: .text) -> .L96 (section: .init.text)

Thank you for this report.  However, given the diff of Honggyu's commit, it
doesn't seem to be the real root cause of this issue.  I also confirmed the
warning is not reproducible with the commit on mm-unstable.

Please let me know if I'm missing something.


Thanks,
SJ

[...]


       reply	other threads:[~2024-07-11  0:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <202407090506.BxtnYHgZ-lkp@intel.com>
2024-07-11  0:32 ` SeongJae Park [this message]
2024-07-11  2:21   ` Philip Li

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=20240711003251.161484-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=honggyu.kim@sk.com \
    --cc=linux-mm@kvack.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