[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240418150721.25d0e82b@namcao>
Date: Thu, 18 Apr 2024 15:07:21 +0200
From: Nam Cao <namcao@...utronix.de>
To: Björn Töpel <bjorn@...nel.org>
Cc: Mike Rapoport <rppt@...nel.org>, Andreas Dilger <adilger@...ger.ca>,
linux-riscv@...ts.infradead.org, Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>, "ndesaulniers @ google . com"
<ndesaulniers@...gle.com>, Luis Chamberlain <mcgrof@...nel.org>, Ingo
Molnar <mingo@...nel.org>, Christophe Leroy <christophe.leroy@...roup.eu>,
Tejun Heo <tj@...nel.org>, Krister Johansen <kjlx@...pleofstupid.com>,
Changbin Du <changbin.du@...wei.com>, Arnd Bergmann <arnd@...db.de>, Geert
Uytterhoeven <geert+renesas@...der.be>, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH] init: fix allocated page overlapping with PTR_ERR
On 2024-04-18 Nam Cao wrote:
> > Mike hints that's *not* the case
> > (https://lore.kernel.org/linux-riscv/ZiAkRMUfiPDUGPdL@kernel.org/).
> > memblock_reserve() should disallow allocation as well, no?
>
> He said it can't be removed if we set max_low_pfn instead of using
> memblock_reserve()
>
> If max_low_pfn() is used, then it can be removed:
^ I mean memblock_reserve()
> https://lore.kernel.org/linux-riscv/Zh6n-nvnQbL-0xss@kernel.org
>
> Best regards,
> Nam
>
Powered by blists - more mailing lists