Dmitry V. Levin 1763fa5f62 s390, s390x: fix printing of syscalls unknown to the kernel
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.
2016-01-13 21:27:48 +00:00
..
2016-01-10 21:38:03 +00:00
2015-11-30 03:30:51 +00:00
2015-11-30 03:30:51 +00:00
2015-11-30 03:30:51 +00:00
2015-12-04 15:03:12 +00:00
2013-02-14 13:39:53 +01:00
2014-02-04 00:03:08 +00:00
2001-08-03 21:51:48 +00:00
2015-03-30 00:33:06 +00:00