Skip to content

config_format: fix SEGV from missing return check #10216

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
Apr 23, 2025

Conversation

DavidKorczynski
Copy link
Contributor

Fixes: https://issues.oss-fuzz.com/issues/42530021


Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

  • [N/A] Example configuration file for the change
  • [N/A] Debug log output from testing the change
  • Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

  • [N/A] Run local packaging test showing all targets (including any new ones) build.
  • [N/A] Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

  • [N/A] Documentation required for this feature

Backporting

  • [N/A] Backport to latest stable release.

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

@DavidKorczynski
Copy link
Contributor Author

CI failure is not due to this PR, can you please take a look @edsiper ?

@leonardo-albertovich
Copy link
Collaborator

I've triggered a CI retry but even if CI keeps failing this is mergeable and should not be delayed.

@edsiper edsiper added this to the Fluent Bit v4.0.1 milestone Apr 23, 2025
@edsiper edsiper merged commit f4ae354 into fluent:master Apr 23, 2025
50 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants