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

pkg/manager: show number of times coverage for each call has overflowed #5520

Merged
merged 2 commits into from
Nov 20, 2024

Conversation

dvyukov
Copy link
Collaborator

@dvyukov dvyukov commented Nov 19, 2024

If the overflows happen often, it's bad.
Add visibility into this.

a-nogikh
a-nogikh previously approved these changes Nov 19, 2024
@dvyukov dvyukov force-pushed the dvyukov-cover-overflow branch 2 times, most recently from 78e12c0 to f5cd48a Compare November 20, 2024 05:04
@dvyukov dvyukov force-pushed the dvyukov-cover-overflow branch 3 times, most recently from a0d26dd to b24d78f Compare November 20, 2024 08:13
a-nogikh
a-nogikh previously approved these changes Nov 20, 2024
pkg/fuzzer/fuzzer.go Outdated Show resolved Hide resolved
If the overflows happen often, it's bad.
Add visibility into this.
The coverage buffer frequently overflows.
We cannot increase it radically b/c they consume lots of memory
(num procs x num kcovs x buffer size) and lead to OOM kills
(at least with 8 procs and 2GB KASAN VM).
So increase it 2x and slightly reduce number of threads/kcov descriptors.
However, in snapshot mode we can be more aggressive (only 1 proc).

This reduces number of overflows by ~~2-4x depending on syscall.
@dvyukov dvyukov added this pull request to the merge queue Nov 20, 2024
Merged via the queue into google:master with commit 4fca165 Nov 20, 2024
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants