s390: keep syscall number / return value in separate pt_regs members

[PATCH RFC 0/2] s390: keep syscall number / return value in separate pt_regs members

Sven Schnelle posted 2 patches 1 week, 3 days ago

Download series mbox

arch/s390/include/asm/ptrace.h  |  9 ++++++---
arch/s390/include/asm/syscall.h | 13 +++++++------
arch/s390/kernel/ptrace.c       |  2 +-
arch/s390/kernel/signal.c       | 12 +++++-------
arch/s390/kernel/syscall.c      | 26 +++++++-------------------
5 files changed, 26 insertions(+), 36 deletions(-)

Expand all Fold all

[PATCH RFC 0/2] s390: keep syscall number / return value in separate pt_regs members

Posted by Sven Schnelle 1 week, 3 days ago

After a recent discussion on the ML about syscall semantics wrt. pre-initializing
the return value to -ENOSYS and the special handling s390 has, I made two patches to
clean that up. See the commit messages for more details.

The second patch is just a cleanup and could be dropped if not wanted.

Sven Schnelle (2):
  s390/syscall: Keep syscall return in extra ptregs member
  s390/syscall: Keep syscall number in extra ptregs member

 arch/s390/include/asm/ptrace.h  |  9 ++++++---
 arch/s390/include/asm/syscall.h | 13 +++++++------
 arch/s390/kernel/ptrace.c       |  2 +-
 arch/s390/kernel/signal.c       | 12 +++++-------
 arch/s390/kernel/syscall.c      | 26 +++++++-------------------
 5 files changed, 26 insertions(+), 36 deletions(-)

-- 
2.53.0