From: Philip Li <philip.li@intel.com>
To: SeongJae Park <sj@kernel.org>
Cc: kernel test robot <lkp@intel.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 7425/10451] WARNING: modpost: vmlinux: section mismatch in reference: devlink_port_rel_cleanup_cb+0x16 (section: .text) -> .L0 (section: .init.text)
Date: Thu, 11 Jul 2024 10:20:24 +0800 [thread overview]
Message-ID: <Zo9BaCRGMigjZwNi@rli9-mobl> (raw)
In-Reply-To: <20240711001614.100561-1-sj@kernel.org>
On Wed, Jul 10, 2024 at 05:16:14PM -0700, SeongJae Park wrote:
> On Tue, 9 Jul 2024 19:07:55 +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: e576342789f1e76ada9fed44f891f5fce83579e9 [7425/10451] mm/damon/core: implement DAMON context commit function
> > config: riscv-randconfig-r033-20230517 (https://download.01.org/0day-ci/archive/20240709/202407091849.4HyNYQIj-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/202407091849.4HyNYQIj-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/202407091849.4HyNYQIj-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>, old ones prefixed by <<):
> >
> [...]
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devlink_port_rel_cleanup_cb+0x16 (section: .text) -> .L0 (section: .init.text)
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devlink_nl_port_attrs_put+0x18 (section: .text) -> .L0 (section: .init.text)
> [...]
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devlink_port_fn_caps_fill+0x2e (section: .text) -> .L0 (section: .init.text)
> [...]
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devlink_port_linecard_set+0xc (section: .text) -> .L0 (section: .init.text)
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devlink_port_function_validate+0x26 (section: .text) -> .L0 (section: .init.text)
> [...]
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devl_port_fn_devlink_set+0x2c (section: .text) -> .L0 (section: .init.text)
> [...]
> > >> WARNING: modpost: vmlinux: section mismatch in reference: __devlink_port_phys_port_name_get+0x1e (section: .text) -> .L0 (section: .init.text)
> [...]
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devlink_port_init+0xe (section: .text) -> .L0 (section: .init.text)
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devlink_port_fini+0xa (section: .text) -> .L0 (section: .init.text)
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devlink_port_attrs_set+0xc (section: .text) -> .L0 (section: .init.text)
> [...]
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devlink_port_attrs_pci_pf_set+0xc (section: .text) -> .L0 (section: .init.text)
> [...]
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devlink_port_attrs_pci_vf_set+0x10 (section: .text) -> .L0 (section: .init.text)
> [...]
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devlink_port_attrs_pci_sf_set+0xc (section: .text) -> .L0 (section: .init.text)
> [...]
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devlink_port_function_set+0x3a (section: .text) -> .L0 (section: .init.text)
> [...]
> > >> WARNING: modpost: vmlinux: section mismatch in reference: devlink_nl_port_split_doit+0x4c (section: .text) -> .L0 (section: .init.text)
>
> Similar to my reply[1] to another similar report, It doesn't look like the
> commit is somewhat to be changed for these new warnings.
>
> Please let me know if I'm missing something.
>
> [1] https://lore.kernel.org/20240711001043.100459-1-sj@kernel.org
Sorry for the false positive, this is a wrong report which seems to only occur on
riscv arch. The bot will be fixed to avoid sending this kind of issues.
>
>
> Thanks,
> SJ
>
prev parent reply other threads:[~2024-07-11 2:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202407091849.4HyNYQIj-lkp@intel.com>
2024-07-11 0:16 ` SeongJae Park
2024-07-11 2:20 ` Philip Li [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=Zo9BaCRGMigjZwNi@rli9-mobl \
--to=philip.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sj@kernel.org \
/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