All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Christian Brauner <christian@brauner.io>,
	torvalds@linux-foundation.org, viro@zeniv.linux.org.uk,
	jannh@google.com, dhowells@redhat.com, oleg@redhat.com,
	linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: serge@hallyn.com, luto@kernel.org, arnd@arndb.de,
	ebiederm@xmission.com, keescook@chromium.org, tglx@linutronix.de,
	mtk.manpages@gmail.com, akpm@linux-foundation.org,
	cyphar@cyphar.com, joel@joelfernandes.org, dancol@google.com
Subject: Re: [PATCH v3 1/4] Make anon_inodes unconditional
Date: Tue, 23 Apr 2019 09:13:31 +0200	[thread overview]
Message-ID: <0dd5adcf-51e9-00a8-cc79-e9bd36b4125e@metux.net> (raw)
In-Reply-To: <20190419120904.27502-2-christian@brauner.io>

On 19.04.19 14:09, Christian Brauner wrote:

Hi,

> From: David Howells <dhowells@redhat.com>
> 
> Make the anon_inodes facility unconditional so that it can be used by core
> VFS code and pidfd code.

I'm not convinced this is necessary. Instead the new features should
select ANON_INODES when enabled. And yes: these features should be
configurable.

Why ? Because embedded folks need to trim down the kernel and drop
everything that's not absolutely needed.


--mtx

-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287

  reply	other threads:[~2019-04-23  7:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-19 12:09 [PATCH v3 0/4] clone: add CLONE_PIDFD Christian Brauner
2019-04-19 12:09 ` [PATCH v3 1/4] Make anon_inodes unconditional Christian Brauner
2019-04-23  7:13   ` Enrico Weigelt, metux IT consult [this message]
2019-04-19 12:09 ` [PATCH v3 2/4] clone: add CLONE_PIDFD Christian Brauner
2019-04-19 12:09 ` [PATCH v3 3/4] signal: support CLONE_PIDFD with pidfd_send_signal Christian Brauner
2019-04-19 12:09 ` [PATCH v3 4/4] samples: show race-free pidfd metadata access Christian Brauner
2019-04-19 15:30   ` Oleg Nesterov
2019-04-19 16:38     ` Christian Brauner
2019-04-19 20:05 ` [PATCH v3 0/4] clone: add CLONE_PIDFD Christian Brauner

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=0dd5adcf-51e9-00a8-cc79-e9bd36b4125e@metux.net \
    --to=lkml@metux.net \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=christian@brauner.io \
    --cc=cyphar@cyphar.com \
    --cc=dancol@google.com \
    --cc=dhowells@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=jannh@google.com \
    --cc=joel@joelfernandes.org \
    --cc=keescook@chromium.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=oleg@redhat.com \
    --cc=serge@hallyn.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.