forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 0
KFuzzTest: refactor and improve input format #8
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
Draft
ethangraham2001
wants to merge
41
commits into
kfuzztest/all
Choose a base branch
from
kfuzztest/relocations-revisited
base: kfuzztest/all
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
WIP. Lots of validation to introduce, and more refactoring so that data doesn't leak.
ethangraham2001
commented
Aug 4, 2025
Export kasan_poison by moving it to include/linux. Move lots of things around into separate .c files to keep kfuzztest.h barebones.
We are going to remove distinct mode in favor of only poisoning the padding areas between payload regions.
Also move functions out of mm/kasan/kasan.h into include/linux/kasan.h
31cbbef to
62053d4
Compare
d286890 to
45f4942
Compare
kfuzztest: update documentation
Checks that KASAN is enabled before poisoning a region.
We now check for overflows a lot more carefully, and validate the input so that regions don't point out of bounds. Fix some nits etc...
We now assume that there is at least 8 bytes of padding before the payload. This means that we never poison the relocation table, which isn't a bad thing in my opinion.
611f62f to
eab275f
Compare
Function now bails out when CONFIG_KASAN is not built in, which prevents checks.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relocation format now uses poisoning. Part of the functionality for this involved
exporting some functions from
mm/kasan/kasan.hfrominclude/linux/kasan.hinstead so that they could be used by KFuzzTest.
Also did some refactoring to make things nicer.
And since we use ranges now, add a macro
KFUZZTEST_REGION_SIZE(n)which can tellus the size of a region, for some optional in-fuzz-driver validation. This could be
real helpful, as we can discard inputs whose buffer sizes are different than the
advertised ones.