From: shuah <shuah@kernel.org>
To: Joel Fernandes <joel@joelfernandes.org>, linux-kernel@vger.kernel.org
Cc: dancol@google.com, minchan@kernel.org,
"Jann Horn" <jannh@google.com>,
"John Stultz" <john.stultz@linaro.org>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Andy Lutomirski" <luto@kernel.org>,
"Hugh Dickins" <hughd@google.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
"Jeff Layton" <jlayton@kernel.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>,
shuah <shuah@kernel.org>
Subject: Re: [PATCH v4 2/2] selftests/memfd: Add tests for F_SEAL_FUTURE_WRITE seal
Date: Mon, 14 Jan 2019 18:39:59 -0700 [thread overview]
Message-ID: <f9ffb7f8-1ff8-3bec-ce79-f9322d8715dc@kernel.org> (raw)
In-Reply-To: <20190112203816.85534-3-joel@joelfernandes.org>
On 1/12/19 1:38 PM, Joel Fernandes wrote:
> From: "Joel Fernandes (Google)" <joel@joelfernandes.org>
>
> Add tests to verify sealing memfds with the F_SEAL_FUTURE_WRITE works as
> expected.
>
> Cc: dancol@google.com
> Cc: minchan@kernel.org
> Cc: Jann Horn <jannh@google.com>
> Cc: John Stultz <john.stultz@linaro.org>
> Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
> ---
Looks good to me. For selftest part of the series:
Reviewed-by: Shuah Khan <shuah@kernel.org>
thanks,
-- Shuah
next prev parent reply other threads:[~2019-01-15 1:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 20:38 [PATCH v4 0/2] Add a future write seal to memfd Joel Fernandes
2019-01-12 20:38 ` [PATCH v4 1/2] mm/memfd: Add an F_SEAL_FUTURE_WRITE " Joel Fernandes
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-15 1:39 ` shuah [this message]
2019-01-15 14:50 ` Joel Fernandes
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=f9ffb7f8-1ff8-3bec-ce79-f9322d8715dc@kernel.org \
--to=shuah@kernel.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=joel@joelfernandes.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=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 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).