Patch "mm: memblock: fix section mismatch warning again" has been added to the 5.11-stable tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This is a note to let you know that I've just added the patch titled

    mm: memblock: fix section mismatch warning again

to the 5.11-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     mm-memblock-fix-section-mismatch-warning-again.patch
and it can be found in the queue-5.11 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.



commit 6f0aa0146e08ccfeaa83af1ee20f03cbce5a2488
Author: Mike Rapoport <rppt@xxxxxxxxxxxxx>
Date:   Wed Mar 24 21:37:50 2021 -0700

    mm: memblock: fix section mismatch warning again
    
    [ Upstream commit a024b7c2850dddd01e65b8270f0971deaf272f27 ]
    
    Commit 34dc2efb39a2 ("memblock: fix section mismatch warning") marked
    memblock_bottom_up() and memblock_set_bottom_up() as __init, but they
    could be referenced from non-init functions like
    memblock_find_in_range_node() on architectures that enable
    CONFIG_ARCH_KEEP_MEMBLOCK.
    
    For such builds kernel test robot reports:
    
       WARNING: modpost: vmlinux.o(.text+0x74fea4): Section mismatch in reference from the function memblock_find_in_range_node() to the function .init.text:memblock_bottom_up()
       The function memblock_find_in_range_node() references the function __init memblock_bottom_up().
       This is often because memblock_find_in_range_node lacks a __init  annotation or the annotation of memblock_bottom_up is wrong.
    
    Replace __init annotations with __init_memblock annotations so that the
    appropriate section will be selected depending on
    CONFIG_ARCH_KEEP_MEMBLOCK.
    
    Link: https://lore.kernel.org/lkml/202103160133.UzhgY0wt-lkp@xxxxxxxxx
    Link: https://lkml.kernel.org/r/20210316171347.14084-1-rppt@xxxxxxxxxx
    Fixes: 34dc2efb39a2 ("memblock: fix section mismatch warning")
    Signed-off-by: Mike Rapoport <rppt@xxxxxxxxxxxxx>
    Reviewed-by: Arnd Bergmann <arnd@xxxxxxxx>
    Reported-by: kernel test robot <lkp@xxxxxxxxx>
    Reviewed-by: David Hildenbrand <david@xxxxxxxxxx>
    Acked-by: Nick Desaulniers <ndesaulniers@xxxxxxxxxx>
    Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
    Signed-off-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
    Signed-off-by: Sasha Levin <sashal@xxxxxxxxxx>

diff --git a/include/linux/memblock.h b/include/linux/memblock.h
index 7643d2dfa959..4ce9c8f9e684 100644
--- a/include/linux/memblock.h
+++ b/include/linux/memblock.h
@@ -460,7 +460,7 @@ static inline void memblock_free_late(phys_addr_t base, phys_addr_t size)
 /*
  * Set the allocation direction to bottom-up or top-down.
  */
-static inline __init void memblock_set_bottom_up(bool enable)
+static inline __init_memblock void memblock_set_bottom_up(bool enable)
 {
 	memblock.bottom_up = enable;
 }
@@ -470,7 +470,7 @@ static inline __init void memblock_set_bottom_up(bool enable)
  * if this is true, that said, memblock will allocate memory
  * in bottom-up direction.
  */
-static inline __init bool memblock_bottom_up(void)
+static inline __init_memblock bool memblock_bottom_up(void)
 {
 	return memblock.bottom_up;
 }



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux