From: Linus Torvalds Date: Sat, 13 Nov 2021 21:14:05 +0000 (-0800) Subject: Merge tag 'virtio-mem-for-5.16' of git://github.com/davidhildenbrand/linux X-Git-Tag: baikal/aarch64/sdk6.1~5284 X-Git-Url: https://git.baikalelectronics.ru/sdk/?a=commitdiff_plain;h=f52401640983e5c6d80447d1aa231eaca8d58567;p=kernel.git Merge tag 'virtio-mem-for-5.16' of git://github.com/davidhildenbrand/linux Pull virtio-mem update from David Hildenbrand: "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: - Removed /dev/kmem in commit 5fe39c43eb31 ("drivers/char: remove /dev/kmem for good") - Disallowed access to virtio-mem device memory via /dev/mem in commit d77d51d8c02 ("virtio-mem: disallow mapping virtio-mem memory via /dev/mem") - Sanitized access to virtio-mem device memory via /proc/kcore in commit 8232c50c1f26 ("fs/proc/kcore: don't read offline sections, logically offline pages and hwpoisoned pages") - Sanitized access to virtio-mem device memory via /proc/vmcore in commit 3e5751b31fbc ("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" * tag 'virtio-mem-for-5.16' of git://github.com/davidhildenbrand/linux: virtio-mem: support VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE --- f52401640983e5c6d80447d1aa231eaca8d58567