-
Notifications
You must be signed in to change notification settings - Fork 18k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testing: fuzzing failed to run if test run with open TCP connections #71560
Comments
fuzzing uses multiple subprocesses (since the processes can crash). that is incompatible with using a fixed port. https://go.dev/doc/security/fuzz/ closing as working as intended. |
----------------------------------------
5 Feb 2025 01:00:42 Sean Liao ***@***.***>:
fuzzing uses multiple subprocesses (since the processes can crash).
that is incompatible with using a fixed port.
https://go.dev/doc/security/fuzz/
closing as working as intended.
—
Reply to this email directly, view it on
GitHub[#71560 (comment)],
or
unsubscribe[https://github.com/notifications/unsubscribe-auth/AAAKSKSISEGDX6E3KP22YTD2OD54LAVCNFSM6AAAAABWPCWDW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZUGY4TENZRGI].
You are receiving this because you authored the thread.
[Tracking
image][https://github.com/notifications/beacon/AAAKSKV3G7KPGS2QESDW2GL2OD54LA5CNFSM6AAAAABWPCWDW2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTU5BI4GQ.gif]
fuzzing uses multiple subprocesses (since the processes can crash).
that is incompatible with using a fixed port.
?
I am not sure this issue have to do with fixed port.
Multiple subprocess, maybe.
I believe I have read the doc. None in the page mention about fixed port
nor sub process, and its consequences.
closing as working as intended.
??
I am sorry, what is going on here?
|
The error means that the program being fuzzed crashed unexpectedly. In your case it most likely crashed because you are using fixed ports, and crashing if opening the port fails. |
Thank you @seankhliao and @ianlancetaylor for the answers. I keep thinking about this issue and I think there are some underlying issues with current fuzzing.
|
Go version
go version devel go1.25-cc874072f3 Mon Feb 3 08:25:31 2025 -0800 linux/amd64
Output of
go env
in your module/workspace:What did you do?
Given the following code and fuzzing test based on Fuzzing tutorial [1]
I believe the same issues has been reported several times,
There are other issues but I am not sure if its related,
The only error that I can trace is there is a broken pipe during ping [2].
[1] https://go.dev/doc/tutorial/fuzz
[2]
go/src/internal/fuzz/worker.go
Line 312 in b07b20f
What did you see happen?
The fuzz process terminated with an error EOF,
What did you expect to see?
Uncomment both of the lines in FuzzReverse,
and run the test again,
The text was updated successfully, but these errors were encountered: