[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1726394] Re: Passes through prctl(PR_SET_SECCOMP, SECC
From: |
Bug Watch Updater |
Subject: |
[Qemu-devel] [Bug 1726394] Re: Passes through prctl(PR_SET_SECCOMP, SECCOMP_MODE_FILTER, address) |
Date: |
Mon, 02 Apr 2018 06:14:09 -0000 |
** Changed in: qemu (Debian)
Status: Confirmed => Fix Released
--
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:
Fix Released
Status in qemu package in Ubuntu:
Fix Released
Status in qemu source package in Xenial:
Won't Fix
Status in qemu source package in Zesty:
Won't Fix
Status in qemu source package in Artful:
Won't Fix
Status in qemu package in Debian:
Fix Released
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-devel] [Bug 1726394] Re: Passes through prctl(PR_SET_SECCOMP, SECCOMP_MODE_FILTER, address),
Bug Watch Updater <=