Skip to content

resolv: Fix incorrect variable used in ares_parse_txt_reply() error c…#8791

Merged
alexey-tikhonov merged 1 commit into
SSSD:masterfrom
kkzhsh:master
Jun 9, 2026
Merged

resolv: Fix incorrect variable used in ares_parse_txt_reply() error c…#8791
alexey-tikhonov merged 1 commit into
SSSD:masterfrom
kkzhsh:master

Conversation

@kkzhsh

@kkzhsh kkzhsh commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

In src/resolv/async_resolv.c, the error handling for ares_parse_txt_reply() checks the wrong variable. After calling ares_parse_txt_reply(), the result is stored in ret, but the code incorrectly checks status
(a previously used variable) instead.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request fixes a bug in src/resolv/async_resolv.c where the return value of ares_parse_txt_reply (ret) was not being checked, and instead, the callback's status parameter was incorrectly evaluated. The code has been corrected to check ret for success. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@alexey-tikhonov

Copy link
Copy Markdown
Member

Thank you, ACK.

@aplopez aplopez left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

ACK.
Thank you.

…heck

Reviewed-by: Alexey Tikhonov <[email protected]>
Reviewed-by: Alejandro López <[email protected]>
@sssd-bot

sssd-bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

The pull request was accepted by @alexey-tikhonov with the following PR CI status:


🟢 CodeQL (success)
🟢 osh-diff-scan:fedora-rawhide-x86_64:upstream (success)
🟢 rpm-build:centos-stream-10-x86_64:upstream (success)
🟢 rpm-build:fedora-43-x86_64:upstream (success)
🟢 rpm-build:fedora-44-x86_64:upstream (success)
🟢 rpm-build:fedora-rawhide-x86_64:upstream (success)
🟢 testing-farm:centos-stream-10-x86_64:upstream (success)
🟢 testing-farm:fedora-43-x86_64:upstream (success)
🟢 testing-farm:fedora-44-x86_64:upstream (success)
🔴 testing-farm:fedora-rawhide-x86_64:upstream (failure)
🟢 Analyze (target) / cppcheck (success)
🟢 Build / freebsd (success)
🟢 Build / make-distcheck (success)
🟢 ci / intgcheck (centos-10) (success)
🟢 ci / intgcheck (fedora-43) (success)
🟢 ci / intgcheck (fedora-44) (success)
🔴 ci / intgcheck (fedora-45) (failure)
🟢 ci / prepare (success)
🔴 ci / system (centos-10) (failure)
🟢 ci / system (fedora-43) (success)
🔴 ci / system (fedora-44) (failure)
🔴 ci / system (fedora-45) (failure)
➖ Coverity scan / coverity (skipped)
🟢 Static code analysis / codeql (success)
🟢 Static code analysis / pre-commit (success)
🟢 Static code analysis / python-system-tests (success)


There are unsuccessful or unfinished checks. Make sure that the failures are not related to this pull request before merging.

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.

4 participants