lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141125201129.GA27167@smipidev>
Date:	Tue, 25 Nov 2014 21:11:29 +0100
From:	Pieter Smith <pieter@...sman.nl>
To:	David Miller <davem@...emloft.net>
Cc:	josh@...htriplett.org, rdunlap@...radead.org,
	alexander.h.duyck@...el.com, viro@...iv.linux.org.uk,
	ast@...mgrid.com, akpm@...ux-foundation.org, beber@...eeweb.net,
	catalina.mocanu@...il.com, dborkman@...hat.com,
	edumazet@...gle.com, ebiederm@...ssion.com, fabf@...net.be,
	fuse-devel@...ts.sourceforge.net, geert@...ux-m68k.org,
	hughd@...gle.com, iulia.manda21@...il.com, JBeulich@...e.com,
	bfields@...ldses.org, jlayton@...chiereds.net,
	linux-api@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org,
	mcgrof@...e.com, mattst88@...il.com, mgorman@...e.de,
	mst@...hat.com, miklos@...redi.hu, netdev@...r.kernel.org,
	oleg@...hat.com, Paul.Durrant@...rix.com,
	paulmck@...ux.vnet.ibm.com, pefoley2@...oley.com, tgraf@...g.ch,
	therbert@...gle.com, trond.myklebust@...marydata.com,
	willemb@...gle.com, xiaoguangrong@...ux.vnet.ibm.com,
	zhenglong.cai@...c.com.cn
Subject: Re: [PATCH v4 0/7] kernel tinification: optionally compile out
 splice family of syscalls (splice, vmsplice, tee and sendfile)

On Tue, Nov 25, 2014 at 02:04:41PM -0500, David Miller wrote:
> From: josh@...htriplett.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.

I would have loved to make them optional individually, but they all are
semantic variations of the same thing: Moving data between fd's without that
data passing through userspace. It therefore isn't surprising that these
syscalls share an underlying entanglement of code (which is where the bulk of
the space saving is to be had).

What a tiny product developer should be asking himself, is: "Do I really need
to efficiently move data between file descriptors?". If the answer no, he can
disable CONFIG_SYSCALL_SPLICE to squeeze an extra 8KB out of his kernel.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ