From: Nam Cao <namcao@linutronix.de>
To: "Björn Töpel" <bjorn@kernel.org>
Cc: Mike Rapoport <rppt@kernel.org>,
Andreas Dilger <adilger@dilger.ca>,
linux-riscv@lists.infradead.org,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
"ndesaulniers @ google . com" <ndesaulniers@google.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Tejun Heo <tj@kernel.org>,
Krister Johansen <kjlx@templeofstupid.com>,
Changbin Du <changbin.du@huawei.com>,
Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] init: fix allocated page overlapping with PTR_ERR
Date: Thu, 18 Apr 2024 15:07:21 +0200 [thread overview]
Message-ID: <20240418150721.25d0e82b@namcao> (raw)
In-Reply-To: <20240418150148.6a0b4664@namcao>
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
>
next prev parent reply other threads:[~2024-04-18 13:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240429125236eucas1p24219f2d332e0267794a2f87dea9f39c4@eucas1p2.samsung.com>
2024-04-18 10:29 ` [PATCH] init: fix allocated page overlapping with PTR_ERR Nam Cao
2024-04-18 10:54 ` Mike Rapoport
2024-04-18 11:12 ` Nam Cao
2024-04-18 12:41 ` Björn Töpel
2024-04-18 13:01 ` Nam Cao
2024-04-18 13:07 ` Nam Cao [this message]
2024-04-29 12:52 ` Joel Granados
2024-04-30 7:31 ` Nam Cao
2024-04-30 8:37 ` Alexandre Ghiti
2024-04-30 13:35 ` Joel Granados
2024-04-30 15:42 ` Joel Granados
2024-05-10 6:35 ` Nam Cao
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=20240418150721.25d0e82b@namcao \
--to=namcao@linutronix.de \
--cc=adilger@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bjorn@kernel.org \
--cc=changbin.du@huawei.com \
--cc=christophe.leroy@csgroup.eu \
--cc=geert+renesas@glider.be \
--cc=kjlx@templeofstupid.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mcgrof@kernel.org \
--cc=mingo@kernel.org \
--cc=ndesaulniers@google.com \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@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