From: Greg KH <gregkh@linuxfoundation.org>
To: jeffxu@chromium.org
Cc: skhan@linuxfoundation.org, keescook@chromium.org,
akpm@linux-foundation.org, dmitry.torokhov@gmail.com,
dverkamp@chromium.org, hughd@google.com, jeffxu@google.com,
jorgelo@chromium.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
jannh@google.com, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v5 5/6] selftests/memfd: add tests for MFD_NOEXEC_SEAL MFD_EXEC
Date: Tue, 6 Dec 2022 17:02:06 +0100 [thread overview]
Message-ID: <Y49nfotbfHdBN+kq@kroah.com> (raw)
In-Reply-To: <20221206152358.1966099-6-jeffxu@google.com>
On Tue, Dec 06, 2022 at 03:23:57PM +0000, jeffxu@chromium.org wrote:
> From: Jeff Xu <jeffxu@chromium.org>
>
> Tests to verify MFD_NOEXEC, MFD_EXEC and vm.memfd_noexec sysctl.
>
> Signed-off-by: Jeff Xu <jeffxu@chromium.org>
> Co-developed-by: Daniel Verkamp <dverkamp@chromium.org>
> Signed-off-by: Daniel Verkamp <dverkamp@chromium.org>
>
> Change-Id: Idccec1141255ca948c849f4efc8ba5e97f78b6eb
Always use checkpatch.pl on your patches so you don't get grumpy
maintainers telling you to run checkpatch.pl on your patches...
thanks,
greg k-h
next prev parent reply other threads:[~2022-12-06 16:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 15:23 [PATCH v5 0/6] mm/memfd: introduce MFD_NOEXEC_SEAL and MFD_EXEC jeffxu
2022-12-06 15:23 ` [PATCH v5 1/6] mm/memfd: add F_SEAL_EXEC jeffxu
2022-12-06 15:23 ` [PATCH v5 2/6] selftests/memfd: add tests for F_SEAL_EXEC jeffxu
2022-12-06 15:23 ` [PATCH v5 3/6] mm/memfd: add MFD_NOEXEC_SEAL and MFD_EXEC jeffxu
2022-12-06 16:04 ` Greg KH
2022-12-06 16:26 ` Jeff Xu
2022-12-06 16:35 ` Greg KH
2022-12-06 17:48 ` Jeff Xu
2022-12-06 23:24 ` Kees Cook
2022-12-06 15:23 ` [PATCH v5 4/6] mm/memfd: Add write seals when apply SEAL_EXEC to executable memfd jeffxu
2022-12-06 15:23 ` [PATCH v5 5/6] selftests/memfd: add tests for MFD_NOEXEC_SEAL MFD_EXEC jeffxu
2022-12-06 16:02 ` Greg KH [this message]
2022-12-06 16:27 ` Jeff Xu
2022-12-06 15:23 ` [PATCH v5 6/6] mm/memfd: security hook for memfd_create jeffxu
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=Y49nfotbfHdBN+kq@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dverkamp@chromium.org \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=jeffxu@chromium.org \
--cc=jeffxu@google.com \
--cc=jorgelo@chromium.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=skhan@linuxfoundation.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.