** Also affects: linux-oem-5.6 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.6 (Ubuntu Eoan)
Status: New => Invalid
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1872047
Title:
kselftest: seccomp kill_after_ptrace() timeout
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.6 package in Ubuntu:
Fix Committed
Status in linux source package in Eoan:
Fix Committed
Status in linux-oem-5.6 source package in Eoan:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Bug description:
[Impact]
While running seccomp_bpf, kill_after_ptrace() gets stuck if we run it
via /usr/bin/timeout (that is the default), until the timeout expires.
This is because /usr/bin/timeout is preventing to properly deliver
signals to ptrace'd children (SIGSYS in this case).
[Test case]
This problem can be easily reproduced by running:
$ sudo make TARGETS=seccomp kselftest
...
# [ RUN ] TRACE_syscall.skip_a#
not ok 1 selftests: seccomp: seccomp_bpf # TIMEOUT
The test is hanging at this point until the timeout expires and then it
reports the timeout error.
[Fix]
This problem can be prevented by passing --foreground to /usr/bin/timeout,
allowing to properly deliver signals to children processes.
[Regression potential]
Not an upstream fix (patch has been sent to the lkml
https://lkml.org/lkml/2020/4/10/153), but the fix is trivial and it's
only affecting the selftests, not the kernel, so regression potential
is minimal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872047/+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
