linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: josh@joshtriplett.org
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	"Pieter Smith" <pieter@boesman.nl>,
	"Alexander Viro" <viro@zeniv.linux.org.uk>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Matt Turner" <mattst88@gmail.com>,
	"Michal Hocko" <mhocko@suse.cz>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	"Fabian Frederick" <fabf@skynet.be>, "Tejun Heo" <tj@kernel.org>,
	蔡正龙 <zhenglong.cai@cs2c.com.cn>,
	"Luis R. Rodriguez" <mcgrof@suse.com>,
	"Peter Foley" <pefoley2@pefoley.com>,
	"Konstantin Khlebnikov" <koct9i@gmail.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	"Oleg Nesterov" <oleg@redhat.com>,
	"Andy Lutomirski" <luto@amacapital.net>,
	"David Herrmann" <dh.herrmann@gmail.com>,
	"Kees Cook" <keescook@chromium.org>,
	linux-fsdevel@vger.kernel.org,
	"open list" <linux-kernel@vger.kernel.org>,
	ABI/API <linux-api@vger.kernel.org>
Subject: Re: [PATCH 2/2] fs: Support compiling out sendfile
Date: Tue, 21 Oct 2014 13:20:30 -0400	[thread overview]
Message-ID: <1413912030.2350.2.camel@redhat.com> (raw)
In-Reply-To: <20141021171814.GA14704@cloud>

On Tue, 2014-10-21 at 10:18 -0700, josh@joshtriplett.org wrote:
> On Tue, Oct 21, 2014 at 08:37:00AM -0700, H. Peter Anvin wrote:
> > On 10/20/2014 02:48 PM, Pieter Smith wrote:
> > > Many embedded systems will not need this syscall, and omitting it
> > > saves space.  Add a new EXPERT config option CONFIG_SENDFILE_SYSCALL
> > > (default y) to support compiling it out.
> > 
> > <bikeshed>
> > I believe these options ought to be CONFIG_SYSCALL_*
> > </bikeshed>
> 
> I agree.  I think people started using CONFIG_*_SYSCALL because of
> things like AUDITSYSCALL 

AUDITSYSCALL audits syscalls.  It doesn't actually implement any
syscalls.  You are right about SYSFS_SYSCALL though...


  parent reply	other threads:[~2014-10-21 18:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20 21:48 [PATCH 1/2] fs: Moved sendfile syscall to own source file Pieter Smith
2014-10-20 21:48 ` [PATCH 2/2] fs: Support compiling out sendfile Pieter Smith
2014-10-20 22:24   ` josh
2014-10-21  7:51     ` Christoph Hellwig
2014-10-21  9:04       ` Josh Triplett
2014-10-21  9:13         ` Christoph Hellwig
2014-10-21  9:50           ` Josh Triplett
     [not found]   ` <54467D9C.2030302@zytor.com>
     [not found]     ` <20141021171814.GA14704@cloud>
2014-10-21 17:20       ` Eric Paris [this message]
2014-10-20 22:03 ` [PATCH 1/2] fs: Moved sendfile syscall to own source file 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=1413912030.2350.2.camel@redhat.com \
    --to=eparis@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dh.herrmann@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=fabf@skynet.be \
    --cc=hpa@zytor.com \
    --cc=josh@joshtriplett.org \
    --cc=keescook@chromium.org \
    --cc=koct9i@gmail.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mattst88@gmail.com \
    --cc=mcgrof@suse.com \
    --cc=mhocko@suse.cz \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=pefoley2@pefoley.com \
    --cc=pieter@boesman.nl \
    --cc=tj@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).