Dmitry V. Levin
1763fa5f62
On s390/s390x, syscalls with NR up to 255 can be implemented directly using "svc NR", for NR >= 256 "svc 0" with %r1=NR is used. The latter method is allowed for NR < 256, too. When the syscall number specified directly or indirectly is recognized by the kernel, i.e. it is less than its NR_syscalls value, it is stored in %r2 and is available to arch_get_scno via s390_regset.gprs[2]. For syscall numbers >= NR_syscalls this register is set to 0, but %r1 remains unchanged and could be used by arch_get_scno via s390_regset.gprs[1] to decide what the syscall number is. * linux/s390/get_scno.c (arch_get_scno): If s390_regset.gprs[2] is zero, take syscall number from s390_regset.gprs[1]. * NEWS: Mention this fix. This fixes Debian bug #485979 and Fedora bug #1298294. |
||
---|---|---|
.. | ||
arch_regs.c | ||
arch_regs.h | ||
arch_sigreturn.c | ||
get_error.c | ||
get_scno.c | ||
get_syscall_args.c | ||
ioctls_arch0.h | ||
ioctls_inc0.h | ||
syscallent.h | ||
userent0.h | ||
userent1.h | ||
userent.h |