lkml.org 
[lkml]   [2019]   [Apr]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH] arm64: mm: fix max_mapnr is assigned the wrong value
Hi Catalin,

Thanks for your reply. In fact, I didn't hit any problem. I just read the code
and found the problem. I see max_mapnr is to only be used in the
generic pfn_valid().
As you said, we do not use it on arm64. So in a sense, the patch is
meaningless.

But I think since it is a problem, why not fix it (Even if max_mapnr
is not be used)?
What is your opinion?

Catalin Marinas <catalin.marinas@arm.com> 于2019年4月1日周一 下午6:44写道:
>
> On Sat, Mar 30, 2019 at 09:13:46PM +0800, Muchun Song wrote:
> > When we not use flat memory, the mem_map will be NULL and
> > pfn_to_page(max_pfn) is a pointer which is located in kernel space. So
> > max_mapnr is assigned a very large number(e.g., 0xffffxxxx_xxxxxxxx) - fix
> > it.
> >
> > Signed-off-by: Muchun Song <smuchun@gmail.com>
> > ---
> > arch/arm64/mm/init.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> > index bc02818fa48b..e86c21a44c88 100644
> > --- a/arch/arm64/mm/init.c
> > +++ b/arch/arm64/mm/init.c
> > @@ -535,7 +535,7 @@ void __init mem_init(void)
> > else
> > swiotlb_force = SWIOTLB_NO_FORCE;
> >
> > - set_max_mapnr(pfn_to_page(max_pfn) - mem_map);
> > + set_max_mapnr(max_pfn - PHYS_PFN_OFFSET);
> >
> > #ifndef CONFIG_SPARSEMEM_VMEMMAP
> > free_unused_memmap();
>
> The patch looks fine but did you actually hit any problem? max_mapnr
> seems to only be used in the generic pfn_valid() which we do not use on
> arm64 (just wondering if it needs a cc stable; it doesn't look like as
> it's not a regression).
>
> --
> Catalin

\
 
 \ /
  Last update: 2019-04-01 16:22    [W:0.048 / U:26.872 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site