| 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
| ||
|
Message-ID: <481BE0E4.7010904@petalogix.com> Date: Sat, 03 May 2008 13:49:56 +1000 From: John Williams <john.williams@...alogix.com> To: monstr@...nam.cz CC: Arnd Bergmann <arnd@...db.de>, Matthew Wilcox <matthew@....cx>, Will Newton <will.newton@...il.com>, Linux Kernel list <linux-kernel@...r.kernel.org>, linux-arch@...r.kernel.org, git@...inx.com, Stephen Neuendorffer <stephen.neuendorffer@...inx.com>, John Linn <John.Linn@...inx.com> Subject: Re: microblaze syscall list Michal, Arnd et al, Michal Simek wrote: >>>> How about this strategy then: >>>> * Change all the data types and syscall numbers in the -for-2.6.27 >>>> branch to only include the minimal set, and a modern ABI >>>> * Add the old interfaces as an out-of-tree patch that adds source >>>> level compatibility with the old libc, but does not modify any >>>> of the new interfaces, so that a patched kernel can run all binaries >>>> built for the upstream version. >>>> * phase out the old source interface gradually, as all users update >>>> their libc source code. >>> >>> Any news on this from the microblaze people? Have you made up your mind >>> on what route you want to go? >> I think we're still digesting it. I need to sync up with Michal and the >> Xilinx people. The libc and kernel API changes have to happen in >> tandem, otherwise Michal can't properly test the kernel he's pushing. >> >> I am the defacto MicroBlaze uClibc and toolchain "builder" but somewhat >> reluctantly - am trying to convince Xilnx to hand that over to someone >> who is expert at it. >> >> Michal, John L, any thoughts? >> >> John > > I am convinced we need to change syscall table. I don't want to maintain old > syscalls. It will be easier to test smaller amount of syscalls. I would like to > talk about with you (John W) via Skype. (Can you send me private email where you > have time?) I talked with Steve about this week. After that I will publish our > proposed way. As a first pass at assessing the C library impact on a completely renovated syscall list, I took Michal's proposed new unistd.h and used it to grep over both the uClibc implementation that (almost) every existing microblaze user uses (!MMU), plus the glibc (cough cough) implementation that is our default with the emerging MMU support. To test the implementation / reference of a syscall number, I grepped the entire source trees for __NR_xxx or _system[0-9](.*xxxx (stripped leading __NR_X) to try and find any mention at all of a particular syscall in that C library implementation. The results are interesting, and verbose. In fact, the lists are so long I'm almost certain I've missed some other obscure way that uClibc or glibc can access a __NR_ macro. Please let me know if this is the case. Certainly there are many implemented in neither, such as as splice and friends. Also interesting is e.g. openat() - it is implemented/referenced by neither! So, surely it would be premature to phase out open() in favour of openat() when the latter is not in any viable MicroBlaze C library yet. I guess we need some help to find the other critical ones. What's also curious is that uClibc not-implemented list is shorter than glibc's. Does this just mean glibc uses fewer of the legacy APIs? I really don't know, but I'm sure someone else does. If there's a cleaner analysis I can do, please let me know and I'll repeat. Here goes - uClibc first, then glibc ** Not implemented/referenced in uClibc 0.9.27 12 January 2005 __NR_add_key __NR_clock_getres __NR_clock_gettime __NR_clock_nanosleep __NR_clock_settime __NR_creat __NR_epoll_pwait __NR_eventfd __NR__exit __NR_exit_group __NR_faccessat __NR_fadvise64_64 __NR_fallocate __NR_fchmodat __NR_fchownat __NR_fstatat64 __NR_fstatfs64 __NR_futex __NR_futimesat __NR_getcpu __NR_get_robust_list __NR_gettid __NR_inotify_add_watch __NR_inotify_init __NR_inotify_rm_watch __NR_io_cancel __NR_io_destroy __NR_io_getevents __NR_ioprio_get __NR_ioprio_set __NR_io_setup __NR_io_submit __NR_kexec_load __NR_keyctl __NR_linkat __NR_lookup_dcookie __NR_mkdirat __NR_mknodat __NR_newfstat __NR_newlstat __NR_newstat __NR_newuname __NR_nfsservctl __NR_openat __NR_ppoll __NR_pselect7 __NR_readahead __NR_readlinkat __NR_removexattrs __NR_renameat __NR_request_key __NR_restart_syscall __NR_rt_sigqueueinfo __NR_sched_getaffinity __NR_sched_setaffinity __NR_semtimedop __NR_set_robust_list __NR_set_tid_address __NR_sgetmask __NR_signal __NR_signalfd __NR_splice __NR_ssetmask __NR_statfs64 __NR_symlinkat __NR_sync_file_range __NR_syscalls __NR_tee __NR_tgkill __NR_timerfd_create __NR_timerfd_gettime __NR_timerfd_settime __NR_tkill __NR_unlinkat __NR_unshare __NR_utimensat __NR_vmsplice __NR_waitid ** Not implemented/referenced in glibc __NR_add_key __NR_adjtimex __NR_alarm __NR_capget __NR_capset __NR_chdir __NR_chown __NR_chroot __NR_close __NR_creat __NR_delete_module __NR_dup __NR_dup2 __NR_epoll_create __NR_epoll_ctl __NR_epoll_pwait __NR_eventfd __NR_execve __NR_faccessat __NR_fallocate __NR_fchdir __NR_fchmod __NR_fchmodat __NR_fchown __NR_fchownat __NR_fdatasync __NR_fgetxattr __NR_flistxattr __NR_flock __NR_fremovexattr __NR_fsetxattr __NR_fstatat64 __NR_fsync __NR_futimesat __NR_getcpu __NR_getegid __NR_geteuid __NR_getgroups __NR_getitimer __NR_getpgid __NR_getpgrp __NR_getppid __NR_getpriority __NR_getrlimit __NR_get_robust_list __NR_getrusage __NR_getsid __NR_gettid __NR_getxattr __NR_init_module __NR_inotify_add_watch __NR_inotify_init __NR_inotify_rm_watch __NR_io_cancel __NR_io_destroy __NR_io_getevents __NR_ioprio_get __NR_ioprio_set __NR_io_setup __NR_io_submit __NR_kexec_load __NR_keyctl __NR_kill __NR_lgetxattr __NR_link __NR_linkat __NR_listxattr __NR_llistxattr __NR_lookup_dcookie __NR_lremovexattr __NR_lseek __NR_lsetxattr __NR_mkdirat __NR_mknodat __NR_mount __NR_msgctl __NR_msgget __NR_msgrcv __NR_msgsnd __NR_munmap __NR_nanosleep __NR_newfstat __NR_newlstat __NR_newstat __NR_newuname __NR_nfsservctl __NR_nice __NR_openat __NR_pause __NR_personality __NR_pivot_root __NR_ppoll __NR_prctl __NR_pselect7 __NR_ptrace __NR_quotactl __NR_read __NR_readlinkat __NR_readv __NR_reboot __NR_removexattrs __NR_renameat __NR_request_key __NR_restart_syscall __NR_sched_getparam __NR_sched_get_priority_max __NR_sched_get_priority_min __NR_sched_getscheduler __NR_sched_rr_get_interval __NR_sched_setparam __NR_sched_setscheduler __NR_sched_yield __NR_semctl __NR_semget __NR_semop __NR_sendfile64 __NR_setdomainname __NR_setgid __NR_setgroups __NR_sethostname __NR_setitimer __NR_setpgid __NR_setpriority __NR_setregid __NR_setreuid __NR_setrlimit __NR_set_robust_list __NR_setsid __NR_settimeofday __NR_setuid __NR_setxattr __NR_sgetmask __NR_shmat __NR_shmctl __NR_shmdt __NR_shmget __NR_signal __NR_signalfd __NR_splice __NR_ssetmask __NR_stime __NR_swapoff __NR_swapon __NR_symlinkat __NR_sync __NR_sync_file_range __NR_syscalls __NR_sysinfo __NR_syslog __NR_tee __NR_time __NR_timerfd_create __NR_timerfd_gettime __NR_timerfd_settime __NR_times __NR_umask __NR_umount __NR_unlink __NR_unlinkat __NR_unshare __NR_uselib __NR_utimensat __NR_vhangup __NR_vmsplice __NR_write __NR_writev > > Michal > > > -- 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