linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Waiman Long <longman@redhat.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Ingo Molnar <mingo@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Justin Forbes <jforbes@redhat.com>,
	Rafael Aquini <aquini@redhat.com>
Subject: Re: [PATCH v2] mm/sparsemem: Fix 'mem_section' will never be NULL gcc 12 warning
Date: Thu, 3 Feb 2022 15:11:57 -0800	[thread overview]
Message-ID: <20220203151157.659f382c76056d883fa80ec6@linux-foundation.org> (raw)
In-Reply-To: <20220202003550.698768-1-longman@redhat.com>

On Tue,  1 Feb 2022 19:35:50 -0500 Waiman Long <longman@redhat.com> wrote:

> The gcc 12 compiler reports a "'mem_section' will never be NULL"
> warning on the following code:
> 
>     static inline struct mem_section *__nr_to_section(unsigned long nr)
>     {
>     #ifdef CONFIG_SPARSEMEM_EXTREME
>         if (!mem_section)
>                 return NULL;
>     #endif
>         if (!mem_section[SECTION_NR_TO_ROOT(nr)])
>                 return NULL;
>        :
> 
> It happens with both CONFIG_SPARSEMEM_EXTREME on and off. The mem_section
> definition is
> 
>     #ifdef CONFIG_SPARSEMEM_EXTREME
>     extern struct mem_section **mem_section;
>     #else
>     extern struct mem_section mem_section[NR_SECTION_ROOTS][SECTIONS_PER_ROOT];
>     #endif
> 
> In the CONFIG_SPARSEMEM_EXTREME case, mem_section obviously cannot
> be NULL, but *mem_section can be if memory hasn't been allocated for
> the dynamic mem_section[] array yet. In the !CONFIG_SPARSEMEM_EXTREME
> case, mem_section is a static 2-dimensional array and so the check
> "!mem_section[SECTION_NR_TO_ROOT(nr)]" doesn't make sense.
> 
> Fix this warning by checking for "!*mem_section" instead of
> "!mem_section" and moving the "!mem_section[SECTION_NR_TO_ROOT(nr)]"
> check up inside the CONFIG_SPARSEMEM_EXTREME block.
> 
> ...
>
> --- a/include/linux/mmzone.h
> +++ b/include/linux/mmzone.h
> @@ -1390,11 +1390,9 @@ static inline unsigned long *section_to_usemap(struct mem_section *ms)
>  static inline struct mem_section *__nr_to_section(unsigned long nr)
>  {
>  #ifdef CONFIG_SPARSEMEM_EXTREME
> -	if (!mem_section)
> +	if (!*mem_section || !mem_section[SECTION_NR_TO_ROOT(nr)])
>  		return NULL;
>  #endif
> -	if (!mem_section[SECTION_NR_TO_ROOT(nr)])
> -		return NULL;
>  	return &mem_section[SECTION_NR_TO_ROOT(nr)][nr & SECTION_ROOT_MASK];
>  }
>  extern size_t mem_section_usage_size(void);

What does the v1->v2 change do?

--- a/include/linux/mmzone.h~mm-sparsemem-fix-mem_section-will-never-be-null-gcc-12-warning-v2
+++ a/include/linux/mmzone.h
@@ -1390,11 +1390,9 @@ static inline unsigned long *section_to_
 static inline struct mem_section *__nr_to_section(unsigned long nr)
 {
 #ifdef CONFIG_SPARSEMEM_EXTREME
-	if (!*mem_section)
+	if (!*mem_section || !mem_section[SECTION_NR_TO_ROOT(nr)])
 		return NULL;
 #endif
-	if (!mem_section[SECTION_NR_TO_ROOT(nr)])
-		return NULL;
 	return &mem_section[SECTION_NR_TO_ROOT(nr)][nr & SECTION_ROOT_MASK];
 }
 extern size_t mem_section_usage_size(void);
_



  reply	other threads:[~2022-02-03 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02  0:35 Waiman Long
2022-02-03 23:11 ` Andrew Morton [this message]
2022-02-04  3:29   ` Waiman Long

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=20220203151157.659f382c76056d883fa80ec6@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aquini@redhat.com \
    --cc=jforbes@redhat.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=longman@redhat.com \
    --cc=mingo@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