From: Andrew Morton <akpm@linux-foundation.org>
To: Jeff Xu <jeffxu@google.com>
Cc: SeongJae Park <sj@kernel.org>,
skhan@linuxfoundation.org, keescook@chromium.org,
dmitry.torokhov@gmail.com, dverkamp@chromium.org,
hughd@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,
linux-security-module@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v7 3/6] mm/memfd: add MFD_NOEXEC_SEAL and MFD_EXEC
Date: Fri, 16 Dec 2022 11:21:02 -0800 [thread overview]
Message-ID: <20221216112102.8eec617257eb90fccb9ff503@linux-foundation.org> (raw)
In-Reply-To: <CALmYWFtfdL=1Nrwyj7je+o8dciDL76CCoga5aE3hZPOh-SFUpA@mail.gmail.com>
On Fri, 16 Dec 2022 11:03:06 -0800 Jeff Xu <jeffxu@google.com> wrote:
> >
> > I just posted a patch for that:
> > https://lore.kernel.org/linux-mm/20221216183314.169707-1-sj@kernel.org/
> >
> > Could you please check?
> >
> Hi SeongJae,
> Thanks for the patch ! I responded to the other thread.
>
> Andrew,
> >From a process point of view, should I update this patch to V9 to
> include the fix ?
> or add a patch directly on top in the mm-unstable branch.
A little fixup patch wouild be preferable.
But I added the below yesterday, so I think we're all good?
--- a/kernel/pid_sysctl.h~mm-memfd-add-mfd_noexec_seal-and-mfd_exec-fix
+++ a/kernel/pid_sysctl.h
@@ -52,8 +52,10 @@ static inline void register_pid_ns_sysct
register_sysctl_paths(vm_path, pid_ns_ctl_table_vm);
}
#else
+static inline void initialize_memfd_noexec_scope(struct pid_namespace *ns) {}
static inline void set_memfd_noexec_scope(struct pid_namespace *ns) {}
static inline void register_pid_ns_ctl_table_vm(void) {}
+static inline void register_pid_ns_sysctl_table_vm(void) {}
#endif
#endif /* LINUX_PID_SYSCTL_H */
_
next prev parent reply other threads:[~2022-12-16 19:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221209160453.3246150-1-jeffxu@google.com>
[not found] ` <20221209160453.3246150-7-jeffxu@google.com>
2022-12-09 17:02 ` [PATCH v7 6/6] mm/memfd: security hook for memfd_create Casey Schaufler
2022-12-09 18:29 ` Paul Moore
2022-12-13 15:00 ` Jeff Xu
2022-12-13 15:37 ` Casey Schaufler
2022-12-13 19:22 ` Paul Moore
2022-12-13 23:05 ` Jeff Xu
2025-09-20 5:54 ` Abhinav Saxena
2025-09-20 18:58 ` Jeff Xu
2022-12-09 18:15 ` [PATCH v7 0/6] mm/memfd: introduce MFD_NOEXEC_SEAL and MFD_EXEC Paul Moore
[not found] ` <20221209160453.3246150-3-jeffxu@google.com>
2022-12-14 18:52 ` [PATCH v7 2/6] selftests/memfd: add tests for F_SEAL_EXEC Kees Cook
2022-12-14 18:54 ` [PATCH v7 0/6] mm/memfd: introduce MFD_NOEXEC_SEAL and MFD_EXEC Kees Cook
2022-12-14 23:32 ` Jeff Xu
2022-12-15 0:08 ` Kees Cook
2022-12-15 16:55 ` Jeff Xu
[not found] ` <20221209160453.3246150-4-jeffxu@google.com>
2022-12-14 18:53 ` [PATCH v7 3/6] mm/memfd: add " Kees Cook
2022-12-16 18:39 ` SeongJae Park
2022-12-16 19:03 ` Jeff Xu
2022-12-16 19:21 ` Andrew Morton [this message]
2022-12-16 19:31 ` SeongJae Park
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=20221216112102.8eec617257eb90fccb9ff503@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dverkamp@chromium.org \
--cc=hughd@google.com \
--cc=jannh@google.com \
--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=linux-security-module@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox