[PATCH] mm,mm_init: Mark set_high_memory as _init

[PATCH] mm,mm_init: Mark set_high_memory as _init

[Oscar Salvador]

set_high_memory() touches arch_zone_lowest_possible_pfn which is
marked as _initdata, which creates a section mismatch.
Since the only user of the function is free_area_init() which is also marked
as _init, mark set_high_memory() as _init as well.

Signed-off-by: Oscar Salvador <osalvador@suse.de>
---
 mm/mm_init.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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();
 
-- 
2.49.0

Re: [PATCH] mm,mm_init: Mark set_high_memory as _init

[Oscar Salvador]

On Tue, May 06, 2025 at 01:10:12PM +0200, Oscar Salvador wrote:
> set_high_memory() touches arch_zone_lowest_possible_pfn which is
> marked as _initdata, which creates a section mismatch.
> Since the only user of the function is free_area_init() which is also marked
> as _init, mark set_high_memory() as _init as well.
> 
> Signed-off-by: Oscar Salvador <osalvador@suse.de>

Of course, the second after I pressed intro I realized I missed:

 Reported-by: kernel test robot <lkp@intel.com>
 Closes: https://lore.kernel.org/oe-kbuild-all/202505060901.Qcs06UoB-lkp@intel.com/

@Andrew: Any chance you could squeeze those? Or should I send v2?

Thanks


-- 
Oscar Salvador
SUSE Labs

Re: [PATCH] mm,mm_init: Mark set_high_memory as _init

[Mike Rapoport]

On Tue, May 06, 2025 at 01:13:16PM +0200, Oscar Salvador wrote:
> On Tue, May 06, 2025 at 01:10:12PM +0200, Oscar Salvador wrote:
> > set_high_memory() touches arch_zone_lowest_possible_pfn which is
> > marked as _initdata, which creates a section mismatch.
> > Since the only user of the function is free_area_init() which is also marked
> > as _init, mark set_high_memory() as _init as well.
> > 
> > Signed-off-by: Oscar Salvador <osalvador@suse.de>
> 
> Of course, the second after I pressed intro I realized I missed:
> 
>  Reported-by: kernel test robot <lkp@intel.com>
>  Closes: https://lore.kernel.org/oe-kbuild-all/202505060901.Qcs06UoB-lkp@intel.com/
> 
> @Andrew: Any chance you could squeeze those? Or should I send v2?

I'll pick this one and add the tags, thanks Oscar.
 
> Thanks
> 
> 
> -- 
> Oscar Salvador
> SUSE Labs

-- 
Sincerely yours,
Mike.

Re: [PATCH] mm,mm_init: Mark set_high_memory as _init

[Mike Rapoport]

From: Mike Rapoport (Microsoft) <rppt@kernel.org>

On Tue, 06 May 2025 13:10:12 +0200, Oscar Salvador wrote:
> set_high_memory() touches arch_zone_lowest_possible_pfn which is
> marked as _initdata, which creates a section mismatch.
> Since the only user of the function is free_area_init() which is also marked
> as _init, mark set_high_memory() as _init as well.
> 
> 

Applied to fixes branch of memblock.git tree, thanks!

[1/1] mm,mm_init: Mark set_high_memory as _init
      commit: 42e31f0daf80d9f7bc4ab4000f2795ec3ddf5206

tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
branch: fixes

--
Sincerely yours,
Mike.

Re: [PATCH] mm,mm_init: Mark set_high_memory as _init

[Oscar Salvador]

On Tue, May 06, 2025 at 08:08:09PM +0300, Mike Rapoport wrote:
> I'll pick this one and add the tags, thanks Oscar.

thank you Mike, appreciated ;-)!
 

-- 
Oscar Salvador
SUSE Labs