diff options
| author | Max Filippov <jcmvbkbc@gmail.com> | 2018-03-30 06:19:58 -0700 |
|---|---|---|
| committer | Max Filippov <jcmvbkbc@gmail.com> | 2018-03-31 14:06:36 -0700 |
| commit | 73a988d957b9142e0a005f4dc87944574f02de51 (patch) | |
| tree | 4b3c4412954601e8969178878132da1f5b9f7db9 /COPYING | |
| parent | 4a6bf7adb92d1b8b7cd3763740b4a5180c0147d5 (diff) | |
| download | qemu-73a988d957b9142e0a005f4dc87944574f02de51.tar.gz | |
linux-user: call cpu_copy under clone_lock
cpu_copy adds newly created CPU object to container/machine/unattached,
but does it w/o proper locking. As a result when multiple threads create
threads rapidly QEMU may abort with the following message:
GLib-CRITICAL **: g_hash_table_iter_next: assertion
'ri->version == ri->hash_table->version' failed
ERROR:qemu/qom/object.c:1663:object_get_canonical_path_component:
code should not be reached
E.g. this issue is observed when running glibc test nptl/tst-eintr1.
Move cpu_copy invocation under clone_lock to fix that.
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions