From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
virtualization@lists.linux-foundation.org,
"Michael S . Tsirkin" <mst@redhat.com>,
David Hildenbrand <david@redhat.com>
Subject: [GIT PULL] virtio-mem changes for v5.16
Date: Wed, 10 Nov 2021 17:37:54 +0100 [thread overview]
Message-ID: <20211110163754.27528-1-david@redhat.com> (raw)
Hi Linus,
usually this would have went via the vhost tree, but as this patch depends
on some patches that just went in via Andrews tree and MST doesn't have
any other patches for this merge window, I'm sending it myself
and base it on current mainline that contains the relevant commits
already. Thanks!
The following changes since commit cb690f5238d71f543f4ce874aa59237cf53a877c:
Merge tag 'for-5.16/drivers-2021-11-09' of git://git.kernel.dk/linux-block (2021-11-09 11:24:08 -0800)
are available in the Git repository at:
https://github.com/davidhildenbrand/linux.git tags/virtio-mem-for-5.16
for you to fetch changes up to 61082ad6a6e1f999eef7e7e90046486c87933b1e:
virtio-mem: support VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE (2021-11-10 15:32:38 +0100)
----------------------------------------------------------------
virtio-mem: support VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE
Support the VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE feature in virtio-mem, now
that "accidential" access to logically unplugged memory inside added
Linux memory blocks is no longer possible, because we:
1. Removed /dev/kmem in commit bbcd53c96071 ("drivers/char: remove
/dev/kmem for good")
2. Disallowed access to virtio-mem device memory via /dev/mem in commit
2128f4e21aa ("virtio-mem: disallow mapping virtio-mem memory via
/dev/mem")
3. Sanitized access to virtio-mem device memory via /proc/kcore in
commit 0daa322b8ff9 ("fs/proc/kcore: don't read offline sections,
logically offline pages and hwpoisoned pages")
4. Sanitized access to virtio-mem device memory via /proc/vmcore in
commit ce2814622e84 ("virtio-mem: kdump mode to sanitize /proc/vmcore
access")
The new VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE feature that will be required
by some hypervisors implementing virtio-mem in the near future, so let's
support it now that we safely can.
Signed-off-by: David Hildenbrand <david@redhat.com>
----------------------------------------------------------------
David Hildenbrand (1):
virtio-mem: support VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE
drivers/virtio/virtio_mem.c | 1 +
include/uapi/linux/virtio_mem.h | 9 ++++++---
2 files changed, 7 insertions(+), 3 deletions(-)
next reply other threads:[~2021-11-10 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 16:37 David Hildenbrand [this message]
2021-11-13 8:54 ` David Hildenbrand
2021-11-13 21:19 ` 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=20211110163754.27528-1-david@redhat.com \
--to=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.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
Powered by JetHome