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: Sat, 7 Nov 2015 01:35:36 +0100 From: Richard Weinberger <richard@....at> To: Octavian Purdila <octavian.purdila@...el.com>, "Richard W.M. Jones" <rjones@...hat.com> Cc: Linux-Arch <linux-arch@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, Hajime Tazaki <thehajime@...il.com> Subject: Re: [RFC PATCH 00/28] Linux Kernel Library Am 04.11.2015 um 15:15 schrieb Octavian Purdila: > We could redefine the syscalls/libc symbols to call lkl_sys_ functions > in launch-lkl, e.g.: > > int opendir(const char *path) > { > return lkl_opendir(new_path) > } To get a better feeling how LKL behaves I've started with a tool to mount any Linux filesystem by FUSE. I.e. such that we can finally automount without root and bugs in filesystem code won't hurt that much. lkl_sys_fstatat64() uses the type struct lkl_stat64. Where is it defined? git grep is unable to locate it. At least it seems to be incompatible with my local struct stat. And why is there no lkl_sys_openat() syscall? Thanks, //richard -- 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