Skip to content

Revert "[libFuzzer] always install signal handler with SA_ONSTACK" #153114

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

Merged
merged 1 commit into from
Aug 12, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 4 additions & 8 deletions compiler-rt/lib/fuzzer/FuzzerUtilPosix.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -78,14 +78,10 @@ static void SetSigaction(int signum,
}

struct sigaction new_sigact = {};
// SA_ONSTACK is required for certain runtimes that use small stacks, for
// instance the Go runtime.
// See https://github.com/golang/go/issues/49075
// Address sanitizer also wants SA_ONSTACK, and the fuzzer and sanitizer
// often run together.
// SA_ONSTACK is a no-op unless someone also calls sigaltstack. That is left
// up to code that needs it.
new_sigact.sa_flags = SA_SIGINFO | SA_ONSTACK;
// Address sanitizer needs SA_ONSTACK (causing the signal handler to run on a
// dedicated stack) in order to be able to detect stack overflows; keep the
// flag if it's set.
new_sigact.sa_flags = SA_SIGINFO | (sigact.sa_flags & SA_ONSTACK);
new_sigact.sa_sigaction = callback;
if (sigaction(signum, &new_sigact, nullptr)) {
Printf("libFuzzer: sigaction failed with %d\n", errno);
Expand Down
Loading