Hi! > People have a number of times noted that there are problems > with syscall(), but I'm not knowledgeable on the details. > I'd happily take a patch to the man page (which, for historical > reasons, is actually syscall(2)) that explains the the problems > (and ideally notes those platforms where there are no problems). Have a look at this commit that tries to deal with passing 64 bit numbers to syscalls. On 32 bit ABI (but not on X32) these needs to be split up (accordingly to machine endianity). https://github.com/linux-test-project/ltp/commit/04afb02b4280a20c262054e8f99a3fad4ad54916 -- Cyril Hrubis chrubis@xxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
