-
Daniel P. Berrangé authored
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>Daniel P. Berrangé authoredRecent 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>
Loading