All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Borislav Petkov <bp@alien8.de>,
	Andrew Morton <akpm@linux-foundation.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: [PATCH 0/3] Do not map unaccepted memory
Date: Wed,  6 Sep 2023 10:38:59 +0300	[thread overview]
Message-ID: <20230906073902.4229-1-adrian.hunter@intel.com> (raw)

Hi

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.

Plug a few gaps where RAM is exposed without checking if it is
unaccepted memory.


Adrian Hunter (3):
      proc/vmcore: Do not map unaccepted memory
      proc/kcore: Do not map unaccepted memory
      /dev/mem: Do not map unaccepted memory

 drivers/char/mem.c |  9 +++++++--
 fs/proc/kcore.c    | 10 +++++++++-
 fs/proc/vmcore.c   | 15 ++++++++++++---
 3 files changed, 28 insertions(+), 6 deletions(-)


Regards
Adrian

WARNING: multiple messages have this Message-ID (diff)
From: Adrian Hunter <adrian.hunter@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Borislav Petkov <bp@alien8.de>,
	Andrew Morton <akpm@linux-foundation.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: [PATCH 0/3] Do not map unaccepted memory
Date: Wed,  6 Sep 2023 10:38:59 +0300	[thread overview]
Message-ID: <20230906073902.4229-1-adrian.hunter@intel.com> (raw)

Hi

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.

Plug a few gaps where RAM is exposed without checking if it is
unaccepted memory.


Adrian Hunter (3):
      proc/vmcore: Do not map unaccepted memory
      proc/kcore: Do not map unaccepted memory
      /dev/mem: Do not map unaccepted memory

 drivers/char/mem.c |  9 +++++++--
 fs/proc/kcore.c    | 10 +++++++++-
 fs/proc/vmcore.c   | 15 ++++++++++++---
 3 files changed, 28 insertions(+), 6 deletions(-)


Regards
Adrian

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

             reply	other threads:[~2023-09-06  7:39 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06  7:38 Adrian Hunter [this message]
2023-09-06  7:38 ` [PATCH 0/3] Do not map unaccepted memory Adrian Hunter
2023-09-06  7:39 ` [PATCH 1/3] proc/vmcore: " Adrian Hunter
2023-09-06  7:39   ` Adrian Hunter
2023-09-07 15:39   ` Dave Hansen
2023-09-07 15:39     ` Dave Hansen
2023-09-07 15:44     ` Adrian Hunter
2023-09-07 15:44       ` Adrian Hunter
2023-09-07 15:51       ` Dave Hansen
2023-09-07 15:51         ` Dave Hansen
2023-09-11  8:03   ` David Hildenbrand
2023-09-11  8:03     ` David Hildenbrand
2023-09-11  8:41     ` Kirill A. Shutemov
2023-09-11  8:41       ` Kirill A. Shutemov
2023-09-11  8:42       ` David Hildenbrand
2023-09-11  8:42         ` David Hildenbrand
2023-09-11  9:27         ` Kirill A. Shutemov
2023-09-11  9:27           ` Kirill A. Shutemov
2023-09-11  9:50           ` David Hildenbrand
2023-09-11  9:50             ` David Hildenbrand
2023-09-11 10:05             ` Kirill A. Shutemov
2023-09-11 10:05               ` Kirill A. Shutemov
2023-09-11 14:33               ` David Hildenbrand
2023-09-11 14:33                 ` David Hildenbrand
2023-09-06  7:39 ` [PATCH 2/3] proc/kcore: " Adrian Hunter
2023-09-06  7:39   ` Adrian Hunter
2023-09-07 15:36   ` Dave Hansen
2023-09-07 15:36     ` Dave Hansen
2023-09-07 15:43   ` Dave Hansen
2023-09-07 15:43     ` Dave Hansen
2023-09-06  7:39 ` [PATCH 3/3] /dev/mem: " Adrian Hunter
2023-09-06  7:39   ` Adrian Hunter
2023-09-07 10:06   ` Kirill A. Shutemov
2023-09-07 10:06     ` Kirill A. Shutemov
2023-09-07 14:15   ` Dave Hansen
2023-09-07 14:15     ` Dave Hansen
2023-09-07 14:25     ` Kirill A. Shutemov
2023-09-07 14:25       ` Kirill A. Shutemov
2023-09-07 14:46       ` Dave Hansen
2023-09-07 14:46         ` Dave Hansen
2023-09-07 15:04         ` Dave Hansen
2023-09-07 15:04           ` Dave Hansen
2023-09-11  8:09         ` David Hildenbrand
2023-09-11  8:09           ` David Hildenbrand
2023-09-11 14:32           ` Dave Hansen
2023-09-11 14:32             ` Dave Hansen
2023-09-07 10:07 ` [PATCH 0/3] " Kirill A. Shutemov
2023-09-07 10:07   ` Kirill A. Shutemov

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=20230906073902.4229-1-adrian.hunter@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=akpm@linux-foundation.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 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.