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

Fuzzing: Gracefully Handle Uninteresting Error to Fix OSS-Fuzz Issue #1952

Merged
merged 1 commit into from
Aug 13, 2024

Conversation

DaveLak
Copy link
Contributor

@DaveLak DaveLak commented Aug 13, 2024

Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=71095

Fuzzing data can generate filenames that trigger:

OSError: [Errno 36] File name too long

The changes here add handling for these exceptions because they di not indicate a bug and should not crash the fuzzer.

…71095

Fuzzing data can generate filenames that trigger:
> OSError: [Errno 36] File name too long

The changes here add handling for these exceptions because they di not
indicate a bug and should not crash the fuzzer.
a
Copy link
Member

@Byron Byron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, thanks for making this work!

It's interesting that the Rust version of this doesn't have this entire class of issues - the only thing that matters are panics, errors like these are considered valid behaviour.

Of course, in Python there is no such differentiation, hence the extra-trouble of having to allow all kinds of exceptions that the fuzzer can legitimately run into.

@Byron Byron merged commit b630eaf into gitpython-developers:main Aug 13, 2024
22 checks passed
@DaveLak DaveLak deleted the fuzzing/issues/71095 branch August 13, 2024 05:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants