summary refs log tree commit diff stats
path: root/results/scraper/fex/1681
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-17 09:10:43 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-07-17 09:10:43 +0200
commitf2ec263023649e596c5076df32c2d328bc9393d2 (patch)
tree5dd86caab46e552bd2e62bf9c4fb1a7504a44db4 /results/scraper/fex/1681
parent63d2e9d409831aa8582787234cae4741847504b7 (diff)
downloadqemu-analysis-main.tar.gz
qemu-analysis-main.zip
add downloaded fex bug-reports HEAD main
Diffstat (limited to 'results/scraper/fex/1681')
-rw-r--r--results/scraper/fex/16818
1 files changed, 8 insertions, 0 deletions
diff --git a/results/scraper/fex/1681 b/results/scraper/fex/1681
new file mode 100644
index 000000000..8fd62462a
--- /dev/null
+++ b/results/scraper/fex/1681
@@ -0,0 +1,8 @@
+std::shared_mutexes can't be safelly locked across forks
+I run into this as part of #1558.

+

+If they are locked before fork, then after fork they may or may not lockup on next lock, semi-randomly.

+

+Looks like we need to roll our own `shared_mutex` implementation.

+

+In general in need a gameplan for fork safety of FEXCore / Syscalls code
\ No newline at end of file