linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	 Christian Brauner <brauner@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org,  Willy Tarreau <w@lwt.eu>,
	Zhangjin Wu <falcon@tinylab.org>
Subject: Re: [PATCH] mm: make MEMFD_CREATE into a selectable config option
Date: Fri, 30 Jun 2023 21:55:47 +0200	[thread overview]
Message-ID: <534f113b-546b-4795-83a1-b87b67727302@t-8ch.de> (raw)
In-Reply-To: <20230630153236.GD11423@frogsfrogsfrogs>

On 2023-06-30 08:32:36-0700, Darrick J. Wong wrote:
> On Fri, Jun 30, 2023 at 11:08:53AM +0200, Thomas Weißschuh wrote:
> > The memfd_create() syscall, enabled by CONFIG_MEMFD_CREATE, is useful on
> > its own even when not required by CONFIG_TMPFS or CONFIG_HUGETLBFS.
> 
> If you don't have tmpfs or hugetlbfs enabled, then what fs ends up
> backing the file returned by memfd_create()?  ramfs?

ramfs, correct.

It goes via mm/memfd.c -> mm/shmem.c -> fs/ramfs/ .

Thomas

> (Not an objection, I'm just curious...)
> 
> --D
> 
> > Split it into its own proper bool option that can be enabled by users.
> > 
> > Move that option into mm/ where the code itself also lies.
> > Also add "select" statements to CONFIG_TMPFS and CONFIG_HUGETLBFS so
> > they automatically enable CONFIG_MEMFD_CREATE as before.
> > 
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> > ---
> >  fs/Kconfig | 5 ++---
> >  mm/Kconfig | 3 +++
> >  2 files changed, 5 insertions(+), 3 deletions(-)

> [..]


  reply	other threads:[~2023-06-30 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30  9:08 Thomas Weißschuh
2023-06-30 13:38 ` Zhangjin Wu
2023-06-30 15:32 ` Darrick J. Wong
2023-06-30 19:55   ` Thomas Weißschuh [this message]
2023-07-03 22:48   ` Mike Kravetz

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=534f113b-546b-4795-83a1-b87b67727302@t-8ch.de \
    --to=thomas@t-8ch.de \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=djwong@kernel.org \
    --cc=falcon@tinylab.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=w@lwt.eu \
    /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