This was blocked migrating on a autopkgtest for a known issue now resolved.
TL;DR no bionic images. Resolved now, should migrate soon.
While the final fix now accepted in linux-user is slightly different,
the difference is only a comment. It is therefore fine if we pick this
up on next merge for Bionic.
Once complete I can plan SRU uploads for this.
** Also affects: qemu (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Xenial)
Status: New => Triaged
** Changed in: qemu (Ubuntu Zesty)
Status: New => Triaged
** Changed in: qemu (Ubuntu Artful)
Status: New => Triaged
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1726394
Title:
Passes through prctl(PR_SET_SECCOMP, SECCOMP_MODE_FILTER, address)
Status in QEMU:
In Progress
Status in qemu package in Ubuntu:
Fix Committed
Status in qemu source package in Xenial:
Triaged
Status in qemu source package in Zesty:
Triaged
Status in qemu source package in Artful:
Triaged
Status in qemu package in Debian:
Confirmed
Bug description:
qemu-user passes through prctl(PR_SET_SECCOMP, SECCOMP_MODE_FILTER,
address) unmodified, but the third argument is an address to a BPF
filter, causing an EFAULT. Now, the filter is architecture-specifc, so
you can't just rewrite the addresses, so the safest bet is to just
return an error here.
I guess you should just return EINVAL, but not sure. I'd really like
something that can be identified, so seccomp errors can be ignored
when it's not supported.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1726394/+subscriptions
