From: Mike Rapoport <rppt@kernel.org>
To: Oscar Salvador <osalvador@suse.de>
Cc: kernel test robot <lkp@intel.com>,
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: WARNING: modpost: vmlinux: section mismatch in reference: set_high_memory+0x8c (section: .text.unlikely) -> zone_movable_pfn (section: .init.data)
Date: Tue, 6 May 2025 11:38:16 +0300 [thread overview]
Message-ID: <aBnKeD-KxlPoAJWM@kernel.org> (raw)
In-Reply-To: <aBm6RKy_AO5iISh1@localhost.localdomain>
On Tue, May 06, 2025 at 09:29:08AM +0200, Oscar Salvador wrote:
> On Tue, May 06, 2025 at 09:42:54AM +0800, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 01f95500a162fca88cefab9ed64ceded5afabc12
> > commit: e120d1bc12da5c1bb871c346f741296610fd6fcb arch, mm: set high_memory in free_area_init()
> > date: 7 weeks ago
> > config: arm-randconfig-r062-20250506 (https://download.01.org/0day-ci/archive/20250506/202505060901.Qcs06UoB-lkp@intel.com/config)
> > compiler: arm-linux-gnueabi-gcc (GCC) 10.5.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250506/202505060901.Qcs06UoB-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/202505060901.Qcs06UoB-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>, old ones prefixed by <<):
> >
> > >> WARNING: modpost: vmlinux: section mismatch in reference: set_high_memory+0x8c (section: .text.unlikely) -> zone_movable_pfn (section: .init.data)
>
> Perhaps?
Looks right, thanks for a quick fix!
Care sending a formal patch?
> diff --git a/mm/mm_init.c b/mm/mm_init.c
> index 80a5370ac6ab..5efec0399e18 100644
> --- a/mm/mm_init.c
> +++ b/mm/mm_init.c
> @@ -1785,7 +1785,7 @@ static bool arch_has_descending_max_zone_pfns(void)
> return IS_ENABLED(CONFIG_ARC) && !IS_ENABLED(CONFIG_ARC_HAS_PAE40);
> }
>
> -static void set_high_memory(void)
> +static void __init set_high_memory(void)
> {
> phys_addr_t highmem = memblock_end_of_DRAM();
>
>
> --
> Oscar Salvador
> SUSE Labs
>
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2025-05-06 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 1:42 kernel test robot
2025-05-06 7:29 ` Oscar Salvador
2025-05-06 8:38 ` Mike Rapoport [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=aBnKeD-KxlPoAJWM@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=osalvador@suse.de \
/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