From: Josh Triplett <josh@joshtriplett.org>
To: kbuild-all@lists.01.org
Subject: Re: [lkp] [+1158 bytes kernel size regression] [i386-tinyconfig] [22dd199a72] mm: introduce secretmemfd system call to create "secret" memory areas
Date: Wed, 22 Jul 2020 20:57:54 -0700 [thread overview]
Message-ID: <20200723035754.GA180721@localhost> (raw)
In-Reply-To: <20200716073259.GD1166045@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
On Thu, Jul 16, 2020 at 10:32:59AM +0300, Mike Rapoport wrote:
> Hi,
>
> On Wed, Jul 15, 2020 at 01:32:02PM -0700, Josh Triplett wrote:
> > On Thu, Jul 16, 2020 at 02:06:18AM +0800, kernel test robot wrote:
> > > commit: 22dd199a7221932b194badb999181ca3fa2e62e2 (mm: introduce secretmemfd system call to create "secret" memory areas)
>
> > Unrelated to the size, I'm wondering: why have this as a separate
> > syscall, rather than just a flag to memfd_create?
>
> Kirill asked the same question but the other way around:
>
> https://lore.kernel.org/linux-mm/20200713105812.dnwtdhsuyj3xbh4f(a)box/
>
> I feel we are going to bikesched about it for a while :)
>
> More seruously, the commonality with memfd_create end at the fact that
> this a file descriptor for memory.
>
> Having this as separate syscall will be less confusing to the users, and
> I beleive, more flexible for future changes.
Fair enough. I'm not going to express a further opinion on the bikeshed
paint color.
That said, please by all means make sure that "make tinyconfig" doesn't
get any bigger with this patch (which *should* be the case as long as
it's a Kconfig option, and no new code gets added outside the Kconfig
option).
- Josh
next parent reply other threads:[~2020-07-23 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200716073259.GD1166045@linux.ibm.com>
2020-07-23 3:57 ` Josh Triplett [this message]
2020-07-15 18:06 [lkp] [+1158 bytes kernel size regression] [i386-tinyconfig] [22dd199a72] mm: introduce secretmemfd system call to create "secret" memory areas kernel test robot
2020-07-15 20:32 ` Josh Triplett
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=20200723035754.GA180721@localhost \
--to=josh@joshtriplett.org \
--cc=kbuild-all@lists.01.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.