Linux NFS development
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: David Miller <davem@davemloft.net>
Cc: josh@joshtriplett.org, rdunlap@infradead.org, pieter@boesman.nl,
	alexander.h.duyck@intel.com, viro@zeniv.linux.org.uk,
	ast@plumgrid.com, akpm@linux-foundation.org, beber@meleeweb.net,
	catalina.mocanu@gmail.com, dborkman@redhat.com,
	edumazet@google.com, fabf@skynet.be,
	fuse-devel@lists.sourceforge.net, geert@linux-m68k.org,
	hughd@google.com, iulia.manda21@gmail.com, JBeulich@suse.com,
	bfields@fieldses.org, jlayton@poochiereds.net,
	linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
	mcgrof@suse.com, mattst88@gmail.com, mgorman@suse.de,
	mst@redhat.com, miklos@szeredi.hu, netdev@vger.kernel.org,
	oleg@redhat.com, Paul.Durrant@citrix.com,
	paulmck@linux.vnet.ibm.com, pefoley2@pefoley.com, tgraf@suug.ch,
	therbert@google.com, trond.myklebust@primarydata.com,
	willemb@google.com, xiaoguangrong@linux.vnet.ibm.com,
	zhenglong.cai@cs2c.com.cn
Subject: Re: [PATCH v4 0/7] kernel tinification: optionally compile out splice family of syscalls (splice, vmsplice, tee and sendfile)
Date: Tue, 25 Nov 2014 14:01:15 -0600	[thread overview]
Message-ID: <87y4qz82yc.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <20141125.142741.1620673255148724338.davem@davemloft.net> (David Miller's message of "Tue, 25 Nov 2014 14:27:41 -0500 (EST)")

David Miller <davem@davemloft.net> writes:

> From: ebiederm@xmission.com (Eric W. Biederman)
> Date: Tue, 25 Nov 2014 13:16:44 -0600
>
>> David Miller <davem@davemloft.net> writes:
>> 
>>> From: josh@joshtriplett.org
>>> Date: Tue, 25 Nov 2014 10:53:10 -0800
>>>
>>>> It's not a "slippery slope"; it's been our standard practice for ages.
>>>
>>> We've never put an entire class of generic system calls behind
>>> a config option.
>> 
>> CONFIG_SYSVIPC has been in the kernel as long as I can remember.
>> 
>> I seem to remember a plan to remove that code once userspace had
>> finished migrating to more unixy interfaces to ipc.  But in 20 years
>> that migration does does not seem to have finished, or even look
>> like it ever will.
>> 
>> But if we started a slippery slope it was long long ago.
>
> Fair enough.
>
> Would be amusing if these tiny systems have it enabled.

It would.

In practice when I was playing in that space I had a hard time
justifying CONFIG_NET and CONFIG_INET.  Despite writing a network
bootloader to use with kexec.

Eric

  reply	other threads:[~2014-11-25 20:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 23:00 [PATCH v4 0/7] kernel tinification: optionally compile out splice family of syscalls (splice, vmsplice, tee and sendfile) Pieter Smith
2014-11-24 23:01 ` [PATCH v4 1/7] fs: move sendfile syscall into fs/splice Pieter Smith
2014-11-24 23:01 ` [PATCH v4 2/7] fs: moved kernel_write to fs/read_write Pieter Smith
2014-11-24 23:01 ` [PATCH v4 3/7] fs/splice: support compiling out splice-family syscalls Pieter Smith
2014-11-25  0:49   ` Josh Triplett
2014-11-24 23:01 ` [PATCH v4 4/7] fs/fuse: support compiling out splice Pieter Smith
2014-11-24 23:01 ` [PATCH v4 5/7] fs/nfsd: " Pieter Smith
2014-11-24 23:01 ` [PATCH v4 6/7] net/core: " Pieter Smith
2014-11-24 23:01 ` [PATCH v4 7/7] fs/splice: full support for " Pieter Smith
2014-11-25  0:52 ` [PATCH v4 0/7] kernel tinification: optionally compile out splice family of syscalls (splice, vmsplice, tee and sendfile) Josh Triplett
     [not found] ` <5474ABB6.3030400@infradead.org>
2014-11-25 17:13   ` David Miller
2014-11-25 18:10     ` Paul E. McKenney
2014-11-25 18:24       ` David Miller
2014-11-25 18:58         ` Theodore Ts'o
2014-11-25 19:05           ` David Miller
2014-11-25 18:53     ` josh
2014-11-25 19:04       ` David Miller
2014-11-25 19:16         ` Eric W. Biederman
2014-11-25 19:27           ` David Miller
2014-11-25 20:01             ` Eric W. Biederman [this message]
2014-11-25 20:11         ` Pieter Smith
2014-11-26 12:19         ` One Thousand Gnomes
2014-11-25 22:08   ` josh

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=87y4qz82yc.fsf@x220.int.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=JBeulich@suse.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.h.duyck@intel.com \
    --cc=ast@plumgrid.com \
    --cc=beber@meleeweb.net \
    --cc=bfields@fieldses.org \
    --cc=catalina.mocanu@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=edumazet@google.com \
    --cc=fabf@skynet.be \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=geert@linux-m68k.org \
    --cc=hughd@google.com \
    --cc=iulia.manda21@gmail.com \
    --cc=jlayton@poochiereds.net \
    --cc=josh@joshtriplett.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=mcgrof@suse.com \
    --cc=mgorman@suse.de \
    --cc=miklos@szeredi.hu \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=pefoley2@pefoley.com \
    --cc=pieter@boesman.nl \
    --cc=rdunlap@infradead.org \
    --cc=tgraf@suug.ch \
    --cc=therbert@google.com \
    --cc=trond.myklebust@primarydata.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willemb@google.com \
    --cc=xiaoguangrong@linux.vnet.ibm.com \
    --cc=zhenglong.cai@cs2c.com.cn \
    /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