From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Song Shuai <songshuaishuai@tinylab.org>,
Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock update for v6.7
Date: Mon, 6 Nov 2023 20:32:58 +0200 [thread overview]
Message-ID: <20231106183258.GP2824@kernel.org> (raw)
Hi Linus,
The following changes since commit 6465e260f48790807eef06b583b38ca9789b6072:
Linux 6.6-rc3 (2023-09-24 14:31:13 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock tags/memblock-v6.7-rc1
for you to fetch changes up to e96c6b8f212a510c9b22362de519f6e1d7920de5:
memblock: report failures when memblock_can_resize is not set (2023-09-28 09:04:33 +0300)
----------------------------------------------------------------
memblock: report failures when memblock_can_resize is not set
Numerous memblock reservations at early boot may exhaust static
memblock.reserved array and it is unnoticed because most of the callers don't
check memblock_reserve() return value.
In this case the system will crash later, but the reason is hard to identify.
Replace return of an error with panic() when memblock.reserved is exhausted
before it can be resized.
----------------------------------------------------------------
Song Shuai (1):
memblock: report failures when memblock_can_resize is not set
mm/memblock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sincerely yours,
Mike.
next reply other threads:[~2023-11-06 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 18:32 Mike Rapoport [this message]
2023-11-08 17:52 ` [GIT PULL] memblock update for v6.7 pr-tracker-bot
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=20231106183258.GP2824@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=songshuaishuai@tinylab.org \
--cc=torvalds@linux-foundation.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