linux-kernel - Re: [RFC PATCH 00/35] remove in-kernel syscall invocations

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: <20180312073256.xo5vdh4ss7g32yma@gmail.com>
Date:   Mon, 12 Mar 2018 08:32:56 +0100
From:   Ingo Molnar <mingo@...nel.org>
To:     Dominik Brodowski <linux@...inikbrodowski.net>
Cc:     linux-kernel@...r.kernel.org, luto@...nel.org,
        torvalds@...ux-foundation.org, viro@...iv.linux.org.uk,
        akpm@...ux-foundation.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC PATCH 00/35] remove in-kernel syscall invocations


* Dominik Brodowski <linux@...inikbrodowski.net> wrote:

> I'm a bit more unsure about these remaining patches. They use inline stubs
> named ksys_xyzzy() which (mostly) call fs-internal functions. Another
> alternative would be to define these in fs/*, but then we'd get more and
> more indirections.
> 
> 	syscalls: do not call sys_unlink() within the kernel
> 	syscalls: do not call sys_rmdir() within the kernel
> 	syscalls: do not call sys_mkdir{,at}() within the kernel
> 	syscalls: do not call sys_symlink{,at}() within the kernel
> 	syscalls: do not call sys_mknod{,at}() within the kernel
> 	syscalls: do not call sys_link{,at}() within the kernel
> 	syscalls: do not call sys_{f,}chmod{at,}() within the kernel
> 	syscalls: do not call sys_{f,}access{,at}() within the kernel
> 	syscalls: do not call sys_ftruncate() within the kernel
> 	syscalls: do not call sys_{,l,f}chown() within the kernel
> 	syscalls: do not call sys_close() within the kernel

>  72 files changed, 572 insertions(+), 274 deletions(-)

Just curious, have you done a before/after vmlinux /usr/bin/size comparison?
How do these changes impact generated code?

My expectation would be for there to be a noticeable decrease in text size.

Thanks,

	Ingo