From: Hari Bathini <hbathini@linux.ibm.com>
To: akpm@linux-foundation.org, david@redhat.com, linux-mm@kvack.org,
mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org
Cc: Hari Bathini <hbathini@linux.ibm.com>,
mike.kravetz@oracle.com, mahesh@linux.ibm.com,
sourabhjain@linux.ibm.com, osalvador@suse.de
Subject: [PATCH v2 0/2] powerpc/fadump: handle CMA activation failure appropriately
Date: Thu, 13 Jan 2022 01:03:38 +0530 [thread overview]
Message-ID: <20220112193340.149020-1-hbathini@linux.ibm.com> (raw)
While commit a4e92ce8e4c8 ("powerpc/fadump: Reservationless firmware
assisted dump"), introduced Linux kernel's Contiguous Memory Allocator
(CMA) based reservation for fadump, it came with the assumption that
the memory remains reserved even if CMA activation fails. It ensures
no kernel pages reside in the reserved memory region, which can't be
mapped into the /proc/vmcore.
But commit 072355c1cf2d ("mm/cma: expose all pages to the buddy if
activation of an area fails") started returning all pages to buddy
allocator if CMA activation fails. This led to warning messages like
below while running crash-utility on vmcore of a kernel having above
two commits:
crash: seek error: kernel virtual address: <from reserved region>
as reserved memory region ended up having kernel pages crash-utility
was looking for. Fix this by introducing an option in CMA, to opt out
from exposing pages to buddy allocator, on CMA activation failure.
Changes in v2:
* Replaced cma->free_pages_on_error with cma->reserve_pages_on_error
& cma_dont_free_pages_on_error() with cma_reserve_pages_on_error()
to avoid confusion and make the expectation on failure clearer.
Hari Bathini (2):
mm/cma: provide option to opt out from exposing pages on activation
failure
powerpc/fadump: opt out from freeing pages on cma activation failure
arch/powerpc/kernel/fadump.c | 6 ++++++
include/linux/cma.h | 2 ++
mm/cma.c | 15 +++++++++++++--
mm/cma.h | 1 +
4 files changed, 22 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2022-01-12 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 19:33 Hari Bathini [this message]
2022-01-12 19:33 ` [PATCH v2 1/2] mm/cma: provide option to opt out from exposing pages on activation failure Hari Bathini
2022-01-13 8:30 ` David Hildenbrand
2022-01-17 7:59 ` Hari Bathini
2022-01-12 19:33 ` [PATCH v2 2/2] powerpc/fadump: opt out from freeing pages on cma " Hari Bathini
2022-01-13 8:31 ` David Hildenbrand
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=20220112193340.149020-1-hbathini@linux.ibm.com \
--to=hbathini@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=mike.kravetz@oracle.com \
--cc=mpe@ellerman.id.au \
--cc=osalvador@suse.de \
--cc=sourabhjain@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).