Public bug reported:
The seccomp man page states the for signals generated by
SECCOMP_RET_TRAP, "The program counter will be as though the system call
happened (i.e., the program counter will not point to the system call
instruction)."
However if x0 (first argument and return value) contains the value -513
(-ERESTARTNOINTR), or if SA_RESTART is enabled on the signal handler and
x0 contains -512 (-ERESTARTSYS) the saved program counter value points
to the system call instruction.
I can reproduce this bug on upstream AArch32 kernels, but not on current
x86-64 kernels.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-1007-aws 5.3.0-1007.8
ProcVersionSignature: User Name 5.3.0-1007.8-aws 5.3.7
Uname: Linux 5.3.0-1007-aws aarch64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: arm64
Date: Sat Nov 30 14:10:31 2019
Ec2AMI: ami-0e88d70910be26319
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-west-1b
Ec2InstanceType: a1.medium
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-aws
UpgradeStatus: Upgraded to eoan on 2019-11-09 (21 days ago)
** Affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug arm64 ec2-images eoan
** Attachment added: "sigsys_test.c"
https://bugs.launchpad.net/bugs/1854574/+attachment/5308878/+files/sigsys_test.c
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1854574
Title:
Seccomp generated SIGSYS has wrong return address if x0 = -513
Status in linux-aws package in Ubuntu:
New
Bug description:
The seccomp man page states the for signals generated by
SECCOMP_RET_TRAP, "The program counter will be as though the system
call happened (i.e., the program counter will not point to the system
call instruction)."
However if x0 (first argument and return value) contains the value
-513 (-ERESTARTNOINTR), or if SA_RESTART is enabled on the signal
handler and x0 contains -512 (-ERESTARTSYS) the saved program counter
value points to the system call instruction.
I can reproduce this bug on upstream AArch32 kernels, but not on
current x86-64 kernels.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-1007-aws 5.3.0-1007.8
ProcVersionSignature: User Name 5.3.0-1007.8-aws 5.3.7
Uname: Linux 5.3.0-1007-aws aarch64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: arm64
Date: Sat Nov 30 14:10:31 2019
Ec2AMI: ami-0e88d70910be26319
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-west-1b
Ec2InstanceType: a1.medium
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-aws
UpgradeStatus: Upgraded to eoan on 2019-11-09 (21 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1854574/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
