From: Jeff Xu <jeffxu@chromium.org>
To: Kees Cook <keescook@chromium.org>
Cc: rdunlap@infradead.org, akpm@linux-foundation.org,
jannh@google.com, sroettger@google.com, willy@infradead.org,
gregkh@linuxfoundation.org, torvalds@linux-foundation.org,
usama.anjum@collabora.com, jeffxu@google.com,
jorgelo@chromium.org, groeck@chromium.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-mm@kvack.org, pedro.falcato@gmail.com,
dave.hansen@intel.com, linux-hardening@vger.kernel.org,
deraadt@openbsd.org
Subject: Re: [PATCH v6 2/4] mseal: add mseal syscall
Date: Sat, 13 Jan 2024 19:48:46 -0800 [thread overview]
Message-ID: <CABi2SkXrUm-oa7bZBxFGHdL6qknAeD0OkLio2vniJw=YgDXQaA@mail.gmail.com> (raw)
In-Reply-To: <202401131146.F017DB5870@keescook>
On Sat, Jan 13, 2024 at 11:48 AM Kees Cook <keescook@chromium.org> wrote:
>
> On Thu, Jan 11, 2024 at 11:41:39PM +0000, jeffxu@chromium.org wrote:
> > diff --git a/include/linux/mm.h b/include/linux/mm.h
> > index f5a97dec5169..345667583b03 100644
> > --- a/include/linux/mm.h
> > +++ b/include/linux/mm.h
> > @@ -30,6 +30,7 @@
> > #include <linux/kasan.h>
> > #include <linux/memremap.h>
> > #include <linux/slab.h>
> > +#include <uapi/linux/mman.h>
>
> I think the arm64 build failure is from this include -- it's happening
> too early and some of the arm defines aren't available yet?
>
good point, I will try fixing it.
Thanks!
-Jeff
> -Kees
>
> --
> Kees Cook
next prev parent reply other threads:[~2024-01-14 3:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 23:41 [PATCH v6 0/4] Introduce mseal() jeffxu
2024-01-11 23:41 ` [PATCH v6 1/4] mseal: Wire up mseal syscall jeffxu
2024-01-11 23:41 ` [PATCH v6 2/4] mseal: add " jeffxu
2024-01-13 19:48 ` Kees Cook
2024-01-14 3:48 ` Jeff Xu [this message]
2024-01-11 23:41 ` [PATCH v6 3/4] selftest mm/mseal memory sealing jeffxu
2024-01-11 23:41 ` [PATCH v6 4/4] mseal:add documentation jeffxu
2024-01-13 1:10 ` Randy Dunlap
2024-01-13 4:51 ` Jeff Xu
2024-01-13 2:19 ` [PATCH v6 0/4] Introduce mseal() Randy Dunlap
2024-01-13 4:53 ` Jeff Xu
2024-01-13 5:57 ` Randy Dunlap
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='CABi2SkXrUm-oa7bZBxFGHdL6qknAeD0OkLio2vniJw=YgDXQaA@mail.gmail.com' \
--to=jeffxu@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=deraadt@openbsd.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--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=pedro.falcato@gmail.com \
--cc=rdunlap@infradead.org \
--cc=sroettger@google.com \
--cc=torvalds@linux-foundation.org \
--cc=usama.anjum@collabora.com \
--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).