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
| ||
|
Date: Sun, 8 Nov 2015 05:49:00 +0200 From: Octavian Purdila <octavian.purdila@...el.com> To: Arnd Bergmann <arnd@...db.de> Cc: Linux-Arch <linux-arch@...r.kernel.org>, lkml <linux-kernel@...r.kernel.org>, Hajime Tazaki <thehajime@...il.com> Subject: Re: [RFC PATCH 08/28] lkl: system call interface and application API On Sun, Nov 8, 2015 at 1:24 AM, Arnd Bergmann <arnd@...db.de> wrote: > On Tuesday 03 November 2015 22:20:39 Octavian Purdila wrote: >> + >> +/* >> + * Unsupported system calls due to lack of support in LKL (e.g. related to >> + * virtual memory, signal, user processes). We also only support 64bit version >> + * of system calls where we have two version to keep the same APi across 32 and >> + * 64 bit hosts. >> + */ >> +#define __NR_restart_syscall 0 >> +#define __NR_exit 0 >> +#define __NR_fork 0 >> +#define __NR_execve 0 >> +#define __NR_ptrace 0 >> +#define __NR_alarm 0 >> +#define __NR_pause 0 > > Why are these not #undef? > >> diff --git a/arch/lkl/include/uapi/asm/unistd.h b/arch/lkl/include/uapi/asm/unistd.h >> new file mode 100644 >> index 0000000..68b5423 >> --- /dev/null >> +++ b/arch/lkl/include/uapi/asm/unistd.h >> @@ -0,0 +1,256 @@ >> +#ifndef _ASM_UAPI_LKL_UNISTD_H >> +#define _ASM_UAPI_LKL_UNISTD_H >> + >> +#ifdef __KERNEL__ >> +#define __NR_ni_syscall 0 >> +#define __NR_reboot 1 >> +#endif >> +#define __NR_getpid 2 >> +#define __NR_write 3 >> +#define __NR_close 4 >> +#define __NR_unlink 5 >> +#define __NR_open 6 >> +#define __NR_poll 7 > > Could you use the standard numbers from include/uapi/asm-generic/unistd.h? > Maybe include that header and then #undef the ones you don't support? > That would avoid having to assign a new number of each future syscall > that gets added. It would be nice to do that but if we undef them warnings will be generated during the build (e.g. "warning: #warning syscall pause not implemented"). Is there a way to disable those warnings? -- 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