summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/kernel/1429313
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
commitd0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
treef8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/kernel/1429313
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloadqemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/kernel/1429313')
-rw-r--r--results/classifier/gemma3:12b/kernel/142931310
1 files changed, 10 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/kernel/1429313 b/results/classifier/gemma3:12b/kernel/1429313
new file mode 100644
index 000000000..3a5853064
--- /dev/null
+++ b/results/classifier/gemma3:12b/kernel/1429313
@@ -0,0 +1,10 @@
+
+qemu-user doesn't block target signals on entry to signal hanlder.
+
+Upon entry to a target signal handler the function process_pending_signals in linux-user/signal.c block the appropriate host signals, but signals already received and queued by Qemu are not blocked. If multiple signals arrive in quick succession this results incorrect recursion in the target signal handler.
+
+The attached test case my be run as:
+
+$ (sleep 2 ; echo) | qemu-i386 ./a.out
+.................. Recursion in signal handler!
+qemu: uncaught target signal 6 (Aborted) - core dumped
\ No newline at end of file