diff options
| author | Daniel P. Berrangé <berrange@redhat.com> | 2021-06-30 15:19:38 +0100 |
|---|---|---|
| committer | Daniel P. Berrangé <berrange@redhat.com> | 2021-07-14 14:15:52 +0100 |
| commit | 2ce949a4c187b2a6aa68ab03216ee271b408fa63 (patch) | |
| tree | c1f389963144c3f79ebce879b1366ac8337d6305 /tests/migration | |
| parent | cfb47f2178c2c9c81870aab0bc0c93e5758cff86 (diff) | |
| download | qemu-2ce949a4c187b2a6aa68ab03216ee271b408fa63.zip qemu-2ce949a4c187b2a6aa68ab03216ee271b408fa63.tar.gz qemu-2ce949a4c187b2a6aa68ab03216ee271b408fa63.tar.bz2 | |
seccomp: don't block getters for resource control syscalls
Recent GLibC calls sched_getaffinity in code paths related to malloc and
when QEMU blocks access, it sends it off into a bad codepath resulting
in stack exhaustion[1]. The GLibC bug is being fixed[2], but none the
less, GLibC has valid reasons to want to use sched_getaffinity.
It is not unreasonable for code to want to run many resource syscalls
for information gathering, so it is a bit too harsh for QEMU to block
them.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1975693
[2] https://sourceware.org/pipermail/libc-alpha/2021-June/128271.html
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Acked-by: Eduardo Otubo <otubo@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Diffstat (limited to 'tests/migration')
0 files changed, 0 insertions, 0 deletions