@pmaydell It's actually https://lists.gnu.org/archive/html/qemu- devel/2017-11/msg00828.html :)
@paelzer It mostly depends how people run a apt 1.6 foreign architecture chroot with the same pointer size as the host architecture - if they install qemu-user inside the chroot, they're fine, if they copy an old version from the outside, they're not. If the copying is common, we might want to SRU that back to xenial and newer I guess. -- 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 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
