[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210527155644.7792b4eaa16ec56645e1080c@linux-foundation.org>
Date: Thu, 27 May 2021 15:56:44 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Catalin Marinas <catalin.marinas@....com>
Cc: Mike Rapoport <rppt@...ux.ibm.com>,
Qian Cai <quic_qiancai@...cinc.com>,
David Hildenbrand <david@...hat.com>,
Anshuman Khandual <anshuman.khandual@....com>,
Ard Biesheuvel <ardb@...nel.org>,
Linux Memory Management List <linux-mm@...ck.org>,
Will Deacon <will@...nel.org>, Marc Zyngier <maz@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: Arm64 crash while reading memory sysfs
On Thu, 27 May 2021 18:50:48 +0100 Catalin Marinas <catalin.marinas@....com> wrote:
> > Can you please try Anshuman's patch "arm64/mm: Drop HAVE_ARCH_PFN_VALID":
> >
> > https://lore.kernel.org/lkml/1621947349-25421-1-git-send-email-anshuman.khandual@arm.com
> >
> > It seems to me that the check for memblock_is_memory() in
> > arm64::pfn_valid() is what makes init_unavailable_range() to bail out for
> > section parts that are not actually populated and then we have
> > VM_BUG_ON_PAGE(PagePoisoned(p)) for these pages.
>
> I acked Anshuman's patch, I think they all need to go in together.
That's neat. Specifically which patches are we referring to here?
Powered by blists - more mailing lists