From: Joel Fernandes <joel@joelfernandes.org>
To: linux-kernel@vger.kernel.org
Cc: "Joel Fernandes (Google)" <joel@joelfernandes.org>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Andy Lutomirski" <luto@kernel.org>,
dancol@google.com, "Hugh Dickins" <hughd@google.com>,
"Jann Horn" <jannh@google.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
"Jeff Layton" <jlayton@kernel.org>,
"John Stultz" <john.stultz@linaro.org>,
linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Matthew Wilcox" <willy@infradead.org>,
"Mike Kravetz" <mike.kravetz@oracle.com>,
minchan@kernel.org, "Shuah Khan" <shuah@kernel.org>
Subject: [PATCH v4 0/2] Add a future write seal to memfd
Date: Sat, 12 Jan 2019 15:38:14 -0500 [thread overview]
Message-ID: <20190112203816.85534-1-joel@joelfernandes.org> (raw)
From: "Joel Fernandes (Google)" <joel@joelfernandes.org>
This is just a resend of the previous series at
https://lore.kernel.org/patchwork/patch/1014892/
with a small if block refactor as Andy suggested:
https://lore.kernel.org/patchwork/comment/1198679/
All,
Could you please provide your Reviewed-by / Acked-by tags?
I will also resend the manpage changes shortly.
Joel Fernandes (Google) (2):
mm/memfd: Add an F_SEAL_FUTURE_WRITE seal to memfd
selftests/memfd: Add tests for F_SEAL_FUTURE_WRITE seal
fs/hugetlbfs/inode.c | 2 +-
include/uapi/linux/fcntl.h | 1 +
mm/memfd.c | 3 +-
mm/shmem.c | 25 +++++++-
tools/testing/selftests/memfd/memfd_test.c | 74 ++++++++++++++++++++++
5 files changed, 100 insertions(+), 5 deletions(-)
--
2.20.1.97.g81188d93c3-goog
WARNING: multiple messages have this Message-ID (diff)
From: joel at joelfernandes.org (Joel Fernandes)
Subject: [PATCH v4 0/2] Add a future write seal to memfd
Date: Sat, 12 Jan 2019 15:38:14 -0500 [thread overview]
Message-ID: <20190112203816.85534-1-joel@joelfernandes.org> (raw)
From: "Joel Fernandes (Google)" <joel at joelfernandes.org>
This is just a resend of the previous series at
https://lore.kernel.org/patchwork/patch/1014892/
with a small if block refactor as Andy suggested:
https://lore.kernel.org/patchwork/comment/1198679/
All,
Could you please provide your Reviewed-by / Acked-by tags?
I will also resend the manpage changes shortly.
Joel Fernandes (Google) (2):
mm/memfd: Add an F_SEAL_FUTURE_WRITE seal to memfd
selftests/memfd: Add tests for F_SEAL_FUTURE_WRITE seal
fs/hugetlbfs/inode.c | 2 +-
include/uapi/linux/fcntl.h | 1 +
mm/memfd.c | 3 +-
mm/shmem.c | 25 +++++++-
tools/testing/selftests/memfd/memfd_test.c | 74 ++++++++++++++++++++++
5 files changed, 100 insertions(+), 5 deletions(-)
--
2.20.1.97.g81188d93c3-goog
WARNING: multiple messages have this Message-ID (diff)
From: joel@joelfernandes.org (Joel Fernandes)
Subject: [PATCH v4 0/2] Add a future write seal to memfd
Date: Sat, 12 Jan 2019 15:38:14 -0500 [thread overview]
Message-ID: <20190112203816.85534-1-joel@joelfernandes.org> (raw)
Message-ID: <20190112203814.0IIk_NJISHgdzfdk8Bh4IjL3KrbHj2zXE812AyHVRWI@z> (raw)
From: "Joel Fernandes (Google)" <joel@joelfernandes.org>
This is just a resend of the previous series at
https://lore.kernel.org/patchwork/patch/1014892/
with a small if block refactor as Andy suggested:
https://lore.kernel.org/patchwork/comment/1198679/
All,
Could you please provide your Reviewed-by / Acked-by tags?
I will also resend the manpage changes shortly.
Joel Fernandes (Google) (2):
mm/memfd: Add an F_SEAL_FUTURE_WRITE seal to memfd
selftests/memfd: Add tests for F_SEAL_FUTURE_WRITE seal
fs/hugetlbfs/inode.c | 2 +-
include/uapi/linux/fcntl.h | 1 +
mm/memfd.c | 3 +-
mm/shmem.c | 25 +++++++-
tools/testing/selftests/memfd/memfd_test.c | 74 ++++++++++++++++++++++
5 files changed, 100 insertions(+), 5 deletions(-)
--
2.20.1.97.g81188d93c3-goog
next reply other threads:[~2019-01-12 20:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 20:38 Joel Fernandes [this message]
2019-01-12 20:38 ` [PATCH v4 0/2] Add a future write seal to memfd Joel Fernandes
2019-01-12 20:38 ` joel
2019-01-12 20:38 ` [PATCH v4 1/2] mm/memfd: Add an F_SEAL_FUTURE_WRITE " Joel Fernandes
2019-01-12 20:38 ` Joel Fernandes
2019-01-12 20:38 ` joel
2019-01-15 17:36 ` John Stultz
2019-01-15 17:36 ` John Stultz
2019-01-15 17:36 ` john.stultz
2019-01-12 20:38 ` [PATCH v4 2/2] selftests/memfd: Add tests for F_SEAL_FUTURE_WRITE seal Joel Fernandes
2019-01-12 20:38 ` Joel Fernandes
2019-01-12 20:38 ` joel
2019-01-15 1:39 ` shuah
2019-01-15 1:39 ` shuah
2019-01-15 1:39 ` shuah
2019-01-15 14:50 ` Joel Fernandes
2019-01-15 14:50 ` Joel Fernandes
2019-01-15 14:50 ` joel
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=20190112203816.85534-1-joel@joelfernandes.org \
--to=joel@joelfernandes.org \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=dancol@google.com \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=jlayton@kernel.org \
--cc=john.stultz@linaro.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=marcandre.lureau@redhat.com \
--cc=mike.kravetz@oracle.com \
--cc=minchan@kernel.org \
--cc=shuah@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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 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.