FYI - this is from http://lists.nongnu.org/archive/html/qemu- devel/2017-11/msg00417.html
Upstream response looks good, but not committed there yet. @Julian - given the case will you need this as an SRU as well or is it only tied to newer apt (or newer apt use cases)? Test queues in Bionic are still stalling this, there was an error on an iso test on s390x which seemed unrelated to the update - I retriggered for now as I'd assume it needs a newer fixed daily iso. -- 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: New Status in qemu package in Ubuntu: Fix Committed 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
