From: "Marc-André Lureau" <marcandre.lureau@redhat.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: aarcange@redhat.com, hughd@google.com, nyc@holomorphy.com,
mike.kravetz@oracle.com,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [PATCH 0/6] memfd: add sealing to hugetlb-backed memory
Date: Tue, 31 Oct 2017 19:30:42 +0100 [thread overview]
Message-ID: <20171031183048.1563-1-marcandre.lureau@redhat.com> (raw)
Hi,
Recently, Mike Kravetz added hugetlbfs support to memfd. However, he
didn't add sealing support. One of the reasons to use memfd is to have
shared memory sealing when doing IPC or sharing memory with another
process with some extra safety. qemu uses shared memory & hugetables
with vhost-user (used by dpdk), so it is reasonable to use memfd
now instead for convenience and security reasons.
Thanks!
RFC->v1:
- split rfc patch, after early review feedback
- added patch for memfd-test changes
- fix build with hugetlbfs disabled
- small code and commit messages improvements
Marc-AndrA(C) Lureau (6):
shmem: unexport shmem_add_seals()/shmem_get_seals()
shmem: rename functions that are memfd-related
hugetlb: expose hugetlbfs_inode_info in header
hugetlbfs: implement memfd sealing
shmem: add sealing support to hugetlb-backed memfd
memfd-tests: test hugetlbfs sealing
fs/fcntl.c | 2 +-
fs/hugetlbfs/inode.c | 39 +++++---
include/linux/hugetlb.h | 11 +++
include/linux/shmem_fs.h | 6 +-
mm/shmem.c | 59 +++++++-----
tools/testing/selftests/memfd/memfd_test.c | 150 +++--------------------------
6 files changed, 89 insertions(+), 178 deletions(-)
--
2.15.0.rc0.40.gaefcc5f6f
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-10-31 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 18:30 Marc-André Lureau [this message]
2017-10-31 18:40 Marc-André Lureau
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=20171031183048.1563-1-marcandre.lureau@redhat.com \
--to=marcandre.lureau@redhat.com \
--cc=aarcange@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=nyc@holomorphy.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