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 v2 0/9] memfd: add sealing to hugetlb-backed memory
Date: Mon, 6 Nov 2017 15:39:35 +0100 [thread overview]
Message-ID: <20171106143944.13821-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!
v1->v2: after Mike review,
- add "memfd-hugetlb:" prefix in memfd-test
- run fuse test on hugetlb backend memory
- rename function memfd_file_get_seals() -> memfd_file_seals_ptr()
- update commit messages
- added reviewed-by tags
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-André Lureau (9):
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
memfd-test: add 'memfd-hugetlb:' prefix when testing hugetlbfs
memfd-test: move common code to a shared unit
memfd-test: run fuse test on hugetlb backend memory
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/Makefile | 5 +
tools/testing/selftests/memfd/common.c | 45 ++++++
tools/testing/selftests/memfd/common.h | 9 ++
tools/testing/selftests/memfd/fuse_test.c | 36 +++--
tools/testing/selftests/memfd/memfd_test.c | 212 ++++---------------------
tools/testing/selftests/memfd/run_fuse_test.sh | 2 +-
tools/testing/selftests/memfd/run_tests.sh | 1 +
12 files changed, 195 insertions(+), 232 deletions(-)
create mode 100644 tools/testing/selftests/memfd/common.c
create mode 100644 tools/testing/selftests/memfd/common.h
--
2.15.0.rc0.40.gaefcc5f6f
next reply other threads:[~2017-11-06 14:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 14:39 Marc-André Lureau [this message]
2017-11-06 14:39 ` [PATCH v2 1/9] shmem: unexport shmem_add_seals()/shmem_get_seals() Marc-André Lureau
2017-11-06 14:39 ` [PATCH v2 2/9] shmem: rename functions that are memfd-related Marc-André Lureau
2017-11-06 14:39 ` [PATCH v2 3/9] hugetlb: expose hugetlbfs_inode_info in header Marc-André Lureau
2017-11-06 14:39 ` [PATCH v2 4/9] hugetlbfs: implement memfd sealing Marc-André Lureau
2017-11-06 14:39 ` [PATCH v2 5/9] shmem: add sealing support to hugetlb-backed memfd Marc-André Lureau
2017-11-06 23:56 ` Mike Kravetz
2017-11-06 14:39 ` [PATCH v2 6/9] memfd-tests: test hugetlbfs sealing Marc-André Lureau
2017-11-07 1:30 ` Mike Kravetz
2017-11-06 14:39 ` [PATCH v2 7/9] memfd-test: add 'memfd-hugetlb:' prefix when testing hugetlbfs Marc-André Lureau
2017-11-07 1:31 ` Mike Kravetz
2017-11-06 14:39 ` [PATCH v2 8/9] memfd-test: move common code to a shared unit Marc-André Lureau
2017-11-07 1:32 ` Mike Kravetz
2017-11-06 14:39 ` [PATCH v2 9/9] memfd-test: run fuse test on hugetlb backend memory Marc-André Lureau
2017-11-07 1:41 ` Mike Kravetz
2017-11-07 12:12 ` Marc-André Lureau
2017-11-07 1:47 ` [PATCH v2 0/9] memfd: add sealing to hugetlb-backed memory Mike Kravetz
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=20171106143944.13821-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;
as well as URLs for NNTP newsgroup(s).