Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Anuradha Weeraman <anuradha@debian.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: avoid shadowing global mem_map in sparse_init_one_section()
Date: Sun, 5 Jul 2026 12:17:10 +0300	[thread overview]
Message-ID: <akohFqkKncFzoupL@kernel.org> (raw)
In-Reply-To: <aklP82yPNq5lA2Na@riviera.anuradha.dev>

On Sat, Jul 04, 2026 at 11:54:51PM +0530, Anuradha Weeraman wrote:
> With W=2, sparse_init_one_section() warns because its mem_map parameter
> shadows the global mem_map declaration in linux/mmzone.h.
> 
> Rename it to section_mem_map to make that scope explicit and avoid the
> shadowing warning.

I suspect that the comment in mmzone.h saying that mem_map is must be
declared for SPARSEMEM is stale and it can be guarded by #ifdef
CONFIG_FLATMEM which will be a more correct fix.
 
> No functional change.
> 
> Signed-off-by: Anuradha Weeraman <anuradha@debian.org>
> ---
>  mm/internal.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/mm/internal.h b/mm/internal.h
> index 181e79f1d6a2..4943def97167 100644
> --- a/mm/internal.h
> +++ b/mm/internal.h
> @@ -957,7 +957,7 @@ void sparse_init(void);
>  int sparse_index_init(unsigned long section_nr, int nid);
>  
>  static inline void sparse_init_one_section(struct mem_section *ms,
> -		unsigned long pnum, struct page *mem_map,
> +		unsigned long pnum, struct page *section_mem_map,
>  		struct mem_section_usage *usage, unsigned long flags)
>  {
>  	unsigned long coded_mem_map;
> @@ -969,7 +969,7 @@ static inline void sparse_init_one_section(struct mem_section *ms,
>  	 * page_to_pfn() on !CONFIG_SPARSEMEM_VMEMMAP can simply subtract it
>  	 * from the page pointer to obtain the PFN.
>  	 */
> -	coded_mem_map = (unsigned long)(mem_map - section_nr_to_pfn(pnum));
> +	coded_mem_map = (unsigned long)(section_mem_map - section_nr_to_pfn(pnum));
>  	VM_WARN_ON_ONCE(coded_mem_map & ~SECTION_MAP_MASK);
>  
>  	ms->section_mem_map &= ~SECTION_MAP_MASK;
> -- 
> 2.53.0
> 
> 

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2026-07-05  9:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-04 18:24 [PATCH] mm: avoid shadowing global mem_map in sparse_init_one_section() Anuradha Weeraman
2026-07-05  9:17 ` Mike Rapoport [this message]
2026-07-06  9:07   ` David Hildenbrand (Arm)

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=akohFqkKncFzoupL@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=anuradha@debian.org \
    --cc=david@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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