From: David Hildenbrand <david@redhat.com>
To: Adrian Hunter <adrian.hunter@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Borislav Petkov <bp@alien8.de>,
Andrew Morton <akpm@linux-foundation.org>,
Ard Biesheuvel <ardb@kernel.org>
Cc: Dave Hansen <dave.hansen@intel.com>,
Vlastimil Babka <vbabka@suse.cz>,
Mike Rapoport <rppt@linux.ibm.com>,
Lorenzo Stoakes <lstoakes@gmail.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Baoquan He <bhe@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
Dave Young <dyoung@redhat.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-coco@lists.linux.dev,
linux-efi@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH V2 1/2] efi/unaccepted: Do not let /proc/vmcore try to access unaccepted memory
Date: Tue, 12 Sep 2023 09:19:38 +0200 [thread overview]
Message-ID: <96f124d6-c1f2-adb3-1d3b-8329e85ff099@redhat.com> (raw)
In-Reply-To: <20230911112114.91323-2-adrian.hunter@intel.com>
On 11.09.23 13:21, Adrian Hunter wrote:
> Support for unaccepted memory was added recently, refer commit dcdfdd40fa82
> ("mm: Add support for unaccepted memory"), whereby a virtual machine may
> need to accept memory before it can be used.
>
> Do not let /proc/vmcore try to access unaccepted memory because it can
> cause the guest to fail.
Oh, hold on. What are the actual side effects of this?
Once we're in the kdump kernel, any guest is already dead. So failing a
guest doesn't apply, no?
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-09-12 7:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 11:21 [PATCH V2 0/2] Do not try to access unaccepted memory Adrian Hunter
2023-09-11 11:21 ` [PATCH V2 1/2] efi/unaccepted: Do not let /proc/vmcore " Adrian Hunter
2023-09-12 7:18 ` David Hildenbrand
2023-09-12 7:19 ` David Hildenbrand [this message]
2023-09-12 7:47 ` Adrian Hunter
2023-09-12 7:50 ` David Hildenbrand
2023-09-11 11:21 ` [PATCH V2 2/2] proc/kcore: Do not " Adrian Hunter
2023-09-12 7:13 ` 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=96f124d6-c1f2-adb3-1d3b-8329e85ff099@redhat.com \
--to=david@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-efi@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=rppt@linux.ibm.com \
--cc=thomas.lendacky@amd.com \
--cc=vbabka@suse.cz \
--cc=vgoyal@redhat.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).