RFC s390: keep syscall number / return value in separate pt_regs members
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | s390/syscall: Keep syscall return in extra ptregs memberarch/ arch/ arch/ | +11 | 2 replies | |
| 2/2 | s390/syscall: Keep syscall number in extra ptregs memberarch/ arch/ arch/ +2 more | +16 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH RFC 0/2] s390: keep syscall number / return value in separate pt_regs members
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(-)
Signature · 1 line
2.53.0