Closed xrivendell7 closed 4 months ago
Hi @xrivendell7,
This happened 700 commits ago. pkg/ipc and the gate logic does not exist whatsoever. I would suggest to update to HEAD.
Hi @dvyukov, I know this this happend long time ago and syz-manager/syz-fuzzer have refactored totally. However, It's hard to transplant my older code to HEAD now. So, I mean, have we encountered similar problems before, or is there a better way to troubleshoot this problem? Because this problem has really bothered me for a long time, and it happens so often that I am very frustrated to handle it. Thanks!
I don't remember any similar symptoms. Maybe something was fixed at some point, you may check commits to pkg/ipc after you base commit.
Hi. Sorry for an old and weird problem I have. I meet a problem with an older syzkaller version, like https://github.com/google/syzkaller/commit/cb976f63e0177b96eb9ce1c631cc5e2c4b4b0759. I developed from this version and added some new functions for research. However, I meet a deadlock when fuzzing for a while, the vm/fuzzer seems deadlocked and does not execute progs anymore, like
I debugged for days but found I opened 4 procs for each vm, and debugged on one of the syz-fuzzer in the vm-0.
All the goroutines for syz-fuzzer:
And I found all 4 procs are waiting for fuzzer gate tickets and causing the syz-fuzzer to freeze.
However, I don't know why, and find that 4 four groups goroutines is stop syz-executor.0
syz-executor.1
syz-executor.2
syz-executor.3
All the executing environment like
For example syz-executor.1: pid: 0,6592
and 1,6600
That syz-executor.1 's parent 6592 is wait for child 6600 which is waiting for
receive_execute
However, the goroutine14/15 is wait atc.cmd.Wait()
andrp.Read
atmakeCommand
.I'm curious, why the go can't execute at
handshake
to let all the proc runs correctly.I just added another Queue to store interesting seeds(progs) and execute them for more power. I don't know why this would cause such a weird situation. What could be the cause of this problem and why stop like above? I also can't figure out the root cause; I'll provide more details for debugging if needed. Thanks!