Skip to content
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

pthread_create crash: gofuzz, cgo, asan, go 1.16 #46467

Open
nigeltao opened this issue May 31, 2021 · 1 comment
Open

pthread_create crash: gofuzz, cgo, asan, go 1.16 #46467

nigeltao opened this issue May 31, 2021 · 1 comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@nigeltao
Copy link
Contributor

nigeltao commented May 31, 2021

As per
google/oss-fuzz#5442

Some Go fuzzer programs (configured with whatever oss-fuzz does to combine Go with the address sanitizer) are crashing with:

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
pthread_create
_cgo_try_pthread_create
pthread_create

The actual Go code under test does not spawn its own goroutines, although it does involve asm code which IIUC is similar to cgo:
https://github.com/google/oss-fuzz/blob/master/projects/go-snappy/fuzz.go
https://github.com/golang/snappy/blob/master/decode.go
https://github.com/golang/snappy/blob/master/decode_amd64.s

Another comment in that 5442 issue says:

This bug happens for every golang project since go 1.16
I think it happened as well in go 1.15 but only for fuzz targets running multiple goroutines

So perhaps the asm thing is unrelated??

Any suggestions on what to try next?


Also posted to https://groups.google.com/g/golang-dev/c/3DrZWztdaX0 but there's not much discussion there.

@dr2chase dr2chase added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jun 1, 2021
@seankhliao seankhliao added this to the Unplanned milestone Aug 20, 2022
@catenacyber
Copy link
Contributor

My best hope is that this is related to #49075

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Development

No branches or pull requests

4 participants