Thread (22 messages) 22 messages, 9 authors, 2006-08-22

Re: [PATCH] introduce kernel_execve function to replace __KERNEL_SYSCALLS__

From: Björn Steinbrink <hidden>
Date: 2006-08-20 20:36:12
Also in: lkml

On 2006.08.20 22:20:28 +0200, Arjan van de Ven wrote:
On Sun, 2006-08-20 at 22:11 +0200, Björn Steinbrink wrote:
quoted
On 2006.08.20 21:50:46 +0200, Arjan van de Ven wrote:
quoted
\
quoted
Could we rename __syscall_return to IS_SYS_ERR (or whatever) and force
kernel syscall users to do the check? That way we could eliminate errno
s/users/user/ .. there's one left that should die out soon ;)
Only one in unistd.h, but throughout the kernel there are quite a few
unless I'm missing something here:
doener@atjola:~/src/kernel/linux-2.6$ grep \ _syscall * -R | \
quoted
grep -v define\\\|undef\\\|clobber | wc -l
116

Are these just going to be replaced by calls to sys_whatever?
they're not the users of this, they're the definitions... ;)
Well, I assume that if some code defines a syscall, it will actually use
it. Of course I meant to ask if the users of those definitions are going
to just call sys_whatever.
For example check_host_supports_tls in arch/um/os-Linux/sys-i386/tls.c
which even uses the global errno (although in that case the whole
else part could probably be just removed).

Björn
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help