Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20230617044036.3985524-1-zhiguangni01@gmail.com>
 <20230616224407.863c74a3dc9d4f1427802f91@linux-foundation.org>
 <CACZJ9cXM9VkJ5=euHphwM5TtX3aZqZ_QynOq10FtrqCxZfZsQA@mail.gmail.com> <20230617070051.GU52412@kernel.org>
In-Reply-To: <20230617070051.GU52412@kernel.org>
From:   Liam Ni <zhiguangni01@gmail.com>
Date:   Sat, 17 Jun 2023 16:59:46 +0800
Message-ID: <CACZJ9cWFyr7MyGWWaGiNYHDb39ZYAmijH90gAH5N8-z4jc2KNw@mail.gmail.com>
Subject: Re: [PATCH] mm/sparse:avoid null pointer access in memory_present()
To:     Mike Rapoport <rppt@kernel.org>
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        dave.hansen@linux.intel.com, luto@kernel.org, peterz@infradead.org,
        tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, x86@kernel.org,
        hpa@zytor.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Sat, 17 Jun 2023 at 15:01, Mike Rapoport <rppt@kernel.org> wrote:
>
> On Sat, Jun 17, 2023 at 02:17:58PM +0800, Liam Ni wrote:
> > On Sat, 17 Jun 2023 at 13:44, Andrew Morton <akpm@linux-foundation.org>=
 wrote:
> > >
> > > On Sat, 17 Jun 2023 14:40:36 +1000 Liam Ni <zhiguangni01@gmail.com> w=
rote:
> > >
> > > > __nr_to_section() may return a null pointer,
> > > > before accessing the member variable section_mem_map,
> > > > we should first determine whether it is a null pointer.
> > > >
> > > > ...
> > > >
> > > > --- a/mm/sparse.c
> > > > +++ b/mm/sparse.c
> > > > @@ -258,7 +258,7 @@ static void __init memory_present(int nid, unsi=
gned long start, unsigned long en
> > > >               set_section_nid(section, nid);
> > > >
> > > >               ms =3D __nr_to_section(section);
> > > > -             if (!ms->section_mem_map) {
> > > > +             if (ms && !ms->section_mem_map) {
> > > >                       ms->section_mem_map =3D sparse_encode_early_n=
id(nid) |
> > > >                                                       SECTION_IS_ON=
LINE;
> > > >                       __section_mark_present(ms, section);
> > >
> > > I'm suspecting that if __nr_to_section() returns NULL here, we should
> > > just panic.  But a null-deref gives the same information, so why chan=
ge
> > > things?
> >
> > Do you mean if ms is a null pointer=EF=BC=8Cms->section_mem_map will ca=
use
> > system panic,so we needn't change?
>
> Yes, if __nr_to_section ever returns NULL the system will crash anyway.

I got it,do we need to print some information by panic()?

>
> --
> Sincerely yours,
> Mike.