From: Qian Cai <cai@redhat•com>
To: Mike Rapoport <rppt@kernel•org>,
Andrew Morton <akpm@linux-foundation•org>
Cc: Alexander Viro <viro@zeniv•linux.org.uk>,
Andy Lutomirski <luto@kernel•org>, Arnd Bergmann <arnd@arndb•de>,
Borislav Petkov <bp@alien8•de>,
Catalin Marinas <catalin.marinas@arm•com>,
Christopher Lameter <cl@linux•com>,
Dan Williams <dan.j.williams@intel•com>,
Dave Hansen <dave.hansen@linux•intel.com>,
David Hildenbrand <david@redhat•com>,
Elena Reshetova <elena.reshetova@intel•com>,
"H. Peter Anvin" <hpa@zytor•com>, Idan Yaniv <idan.yaniv@ibm•com>,
Ingo Molnar <mingo@redhat•com>,
James Bottomley <jejb@linux•ibm.com>,
"Kirill A. Shutemov" <kirill@shutemov•name>,
Matthew Wilcox <willy@infradead•org>,
Mark Rutland <mark.rutland@arm•com>,
Mike Rapoport <rppt@linux•ibm.com>,
Michael Kerrisk <mtk.manpages@gmail•com>,
Palmer Dabbelt <palmer@dabbelt•com>,
Paul Walmsley <paul.walmsley@sifive•com>,
Peter Zijlstra <peterz@infradead•org>,
Thomas Gleixner <tglx@linutronix•de>,
Tycho Andersen <tycho@tycho•ws>, Will Deacon <will@kernel•org>,
linux-api@vger•kernel.org, linux-arch@vger•kernel.org,
linux-arm-kernel@lists•infradead.org,
linux-fsdevel@vger•kernel.org, linux-mm@kvack•org,
linux-kernel@vger•kernel.org, linux-nvdimm@lists•01.org,
linux-riscv@lists•infradead.org, x86@kernel•org,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org
Subject: Re: [PATCH v5 0/5] mm: introduce memfd_secret system call to create "secret" memory areas
Date: Fri, 18 Sep 2020 14:25:15 -0400 [thread overview]
Message-ID: <fdd0240c187f974fccc553acea895f638d5e822a.camel@redhat.com> (raw)
In-Reply-To: <5d97da4d86db258fdc9b20be3c12588089e17da2.camel@redhat.com>
On Thu, 2020-09-17 at 09:27 -0400, Qian Cai wrote:
> On Wed, 2020-09-16 at 10:35 +0300, Mike Rapoport wrote:
> > From: Mike Rapoport <rppt@linux•ibm.com>
> >
> > Hi,
> >
> > This is an implementation of "secret" mappings backed by a file descriptor.
> > I've dropped the boot time reservation patch for now as it is not strictly
> > required for the basic usage and can be easily added later either with or
> > without CMA.
>
> On powerpc: https://gitlab.com/cailca/linux-mm/-/blob/master/powerpc.config
>
> There is a compiling warning from the today's linux-next:
>
> <stdin>:1532:2: warning: #warning syscall memfd_secret not implemented [-Wcpp]
This should silence the warning:
diff --git a/scripts/checksyscalls.sh b/scripts/checksyscalls.sh
index a18b47695f55..b7609958ee36 100755
--- a/scripts/checksyscalls.sh
+++ b/scripts/checksyscalls.sh
@@ -40,6 +40,10 @@ cat << EOF
#define __IGNORE_setrlimit /* setrlimit */
#endif
+#ifndef __ARCH_WANT_MEMFD_SECRET
+#define __IGNORE_memfd_secret
+#endif
+
/* Missing flags argument */
#define __IGNORE_renameat /* renameat2 */
next prev parent reply other threads:[~2020-09-18 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200916073539.3552-1-rppt@kernel.org>
2020-09-17 13:27 ` [PATCH v5 0/5] mm: introduce memfd_secret system call to create "secret" memory areas Qian Cai
2020-09-18 18:25 ` Qian Cai [this message]
2020-09-21 8:07 ` Stephen Rothwell
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=fdd0240c187f974fccc553acea895f638d5e822a.camel@redhat.com \
--to=cai@redhat$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=bp@alien8$(echo .)de \
--cc=catalin.marinas@arm$(echo .)com \
--cc=cl@linux$(echo .)com \
--cc=dan.j.williams@intel$(echo .)com \
--cc=dave.hansen@linux$(echo .)intel.com \
--cc=david@redhat$(echo .)com \
--cc=elena.reshetova@intel$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=idan.yaniv@ibm$(echo .)com \
--cc=jejb@linux$(echo .)ibm.com \
--cc=kirill@shutemov$(echo .)name \
--cc=linux-api@vger$(echo .)kernel.org \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-nvdimm@lists$(echo .)01.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=luto@kernel$(echo .)org \
--cc=mark.rutland@arm$(echo .)com \
--cc=mingo@redhat$(echo .)com \
--cc=mtk.manpages@gmail$(echo .)com \
--cc=palmer@dabbelt$(echo .)com \
--cc=paul.walmsley@sifive$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=rppt@kernel$(echo .)org \
--cc=rppt@linux$(echo .)ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
--cc=tycho@tycho$(echo .)ws \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=will@kernel$(echo .)org \
--cc=willy@infradead$(echo .)org \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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