In article <20150927143642.gb23...@snowdrop.l8s.co.uk>, David Laight <da...@l8s.co.uk> wrote: >On Thu, Sep 24, 2015 at 10:30:52AM -0400, Christos Zoulas wrote: >> Module Name: src >> Committed By: christos >> Date: Thu Sep 24 14:30:52 UTC 2015 >> >> Modified Files: >> src/sys/kern: makesyscalls.sh >> >> Log Message: >> create an array of altsyscallnames, which are the syscall names that the >> libc api uses. For example syscallnames[293] = "__sigprocmask14", >> altsyscallnames[293] = "sigprocmask". This is so that things like dtrace >> can use the system call names everyone uses. The array is sparse; if the >> names were the same (or for compat names) they are not copied and the array >> has NULL for them. > >Hmmmm.... >Isn't that going to be even more confusing since you won't know >whether a 'compat' (or old) system call is being used which might >have issues in the compatibility layer itself.
Yes, you always do know. All the compat names start with compat_. The kernel names don't need to match what userland needs. christos
