On Wed, Aug 22, 2012 at 11:56:15AM -0400, Mike Frysinger wrote: > Starting with linux 3.6 (and backported to earlier kernels), these two > syscalls have changed numbers (moving from native to compat entry points). > Update the strace syscall list accordingly.
What will happen with applications using old syscall numbers (if any)? Will they get ENOSYS? > * linux/x32/syscallent.h: Move setsockopt from 54 to 541, and move > getsockopt from 55 to 542. > > Signed-off-by: Mike Frysinger <[email protected]> > --- > Note: I'm not sure about the old entry points. Should they get relabeled > as "old" ? Or just leave them as is ? From one side, the rule is to stick to __NR_* names as close as possible. From another side, it's desirable to decode syscalls on older kernels properly. So maybe we should rather leave old entry points for compatibility. -- ldv
pgpWYmzHOTTXY.pgp
Description: PGP signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Strace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/strace-devel
