[PATCH v8 4/9] mm: introduce memfd_secret system call to create "secret" memory areas
Mike Rapoport
rppt at kernel.org
Sun Nov 15 03:45:39 EST 2020
On Fri, Nov 13, 2020 at 02:06:56PM +0000, Matthew Wilcox wrote:
> On Tue, Nov 10, 2020 at 05:14:39PM +0200, Mike Rapoport wrote:
> > diff --git a/mm/Kconfig b/mm/Kconfig
> > index c89c5444924b..d8d170fa5210 100644
> > --- a/mm/Kconfig
> > +++ b/mm/Kconfig
> > @@ -884,4 +884,7 @@ config ARCH_HAS_HUGEPD
> > config MAPPING_DIRTY_HELPERS
> > bool
> >
> > +config SECRETMEM
> > + def_bool ARCH_HAS_SET_DIRECT_MAP && !EMBEDDED
>
> So I now have to build this in, whether I want it or not?
Why wouldn't anybody want this nice feature? ;-)
Now, seriously, I hesitated a lot about having a prompt here, but in the
end I've decided to go without it.
The added footprint is not so big, with x86 defconfig it's less than 8K
and with distro (I've checked with Fedora) config the difference is less
than 1k because they anyway have CMA=y.
As this is "security" feature, disros most probably would have this
enabled anyway, and I believe users that will see something like "Allow
hiding memory from the kernel" will hit Y there.
--
Sincerely yours,
Mike.
More information about the linux-riscv
mailing list