I worked around this in APT for now by ignoring EFAULT or rather,
printing a warning. It would be nice to not do this though.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Importance: Undecided => Medium
** Changed in: qemu (Ubuntu)
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:
New
Status in qemu package in Ubuntu:
Triaged
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
