linux-kernel - Re: [PATCH v4 1/2] init: add sys-wrapper.h

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: <201009181127.47063.arnd@arndb.de>
Date:	Sat, 18 Sep 2010 11:27:46 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Namhyung Kim <namhyung@...il.com>, Sam Ravnborg <sam@...nborg.org>,
	Phillip Lougher <phillip@...gher.demon.co.uk>,
	Al Viro <viro@...iv.linux.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 1/2] init: add sys-wrapper.h

On Friday 17 September 2010, Andrew Morton wrote:
> > -     int err = sys_mount(name, "/root", fs, flags, data);
> > +     int err = kernel_sys_mount(name, "/root", fs, flags, data);
> 
> It would be good if we could arrange for all kernel syscalls to use
> the wrappers.  ie: cause a direct call to sys_mount() to not compile?
> 
> I don't know how practical that would be.

One common reason to call a sys_* function is to implement another
system call, e.g. sys_socketcall calling sys_socket or
compat_sys_timer_create calling sys_timer_create.

I think in those cases we don't really want to go through another
wrapper.

	Arnd
--
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/