All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mike Rapopoprt <rppt@kernel.org>,
	Yajun Deng <yajun.deng@linux.dev>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] memblock: fix crash when reserved memory is not added to memory
Date: Sun, 28 Jan 2024 08:42:16 +0200	[thread overview]
Message-ID: <ZbX3SHT2H_aqHnGW@kernel.org> (raw)

Hi Linus,

The following changes since commit 0dd3ee31125508cd67f7e7172247f05b7fd1753a:

  Linux 6.7 (2024-01-07 12:18:38 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock tags/fixes-2024-01-28

for you to fetch changes up to 6a9531c3a88096a26cf3ac582f7ec44f94a7dcb2:

  memblock: fix crash when reserved memory is not added to memory (2024-01-19 10:53:59 +0200)

----------------------------------------------------------------
memblock: fix crash when reserved memory is not added to memory

When CONFIG_DEFERRED_STRUCT_PAGE_INIT is enabled, the initialization of
reserved pages may cause access of NODE_DATA() with invalid nid and crash.

Add a fall back to early_pfn_to_nid() in memmap_init_reserved_pages() to
ensure a valid node id is always passed to init_reserved_page().

----------------------------------------------------------------
Yajun Deng (1):
      memblock: fix crash when reserved memory is not added to memory

 mm/memblock.c | 3 +++
 1 file changed, 3 insertions(+)


             reply	other threads:[~2024-01-28  6:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-28  6:42 Mike Rapoport [this message]
2024-01-28 18:47 ` [GIT PULL] memblock: fix crash when reserved memory is not added to memory 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=ZbX3SHT2H_aqHnGW@kernel.org \
    --to=rppt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yajun.deng@linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.