Skip to content

utils: do not use errno after success#2046

Draft
eriksjolund wants to merge 1 commit intocontainers:mainfrom
eriksjolund:fix-errno-use
Draft

utils: do not use errno after success#2046
eriksjolund wants to merge 1 commit intocontainers:mainfrom
eriksjolund:fix-errno-use

Conversation

@eriksjolund
Copy link
Contributor

I noticed this when reading the source code.

Signed-off-by: Erik Sjölund <erik.sjolund@gmail.com>
@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the error handling logic within a utility function by ensuring that the errno global variable is only consulted and reported when a preceding operation has explicitly indicated a failure. This change prevents the reporting of stale or irrelevant error codes, leading to more accurate and reliable error diagnostics.

Highlights

  • Error Handling: Corrected the usage of errno in the create_file_if_missing_at function to ensure it is only read and passed to the error reporting mechanism when an actual error has occurred, preventing potentially misleading error codes.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • src/libcrun/utils.c
    • Modified the crun_make_error call to conditionally pass errno based on the return value of the operation, ensuring errno is only used after a failure.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

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

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 aims to fix incorrect errno usage after a successful function call. The change is correct in principle, but it leads to a loss of information in error messages. I've suggested an alternative approach that preserves the original error information while still being correct regarding errno usage.

return 0;

return crun_make_error (err, errno, "create file `%s`", file);
return crun_make_error (err, ret ? errno : 0, "create file `%s`", file);

Choose a reason for hiding this comment

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

medium

While this change correctly avoids using errno after a successful function call (get_file_type_at), it replaces the original error from openat with 0. This loses valuable information. For instance, if openat failed because a directory with the same name exists (EISDIR), this information would be lost.

A better approach, consistent with other parts of this file (e.g., line 227), is to save errno after the failing openat call and use it later.

I recommend an implementation like this:

if (fd_write < 0)
  {
    int saved_errno = errno;
    mode_t tmp_mode;
    int ret;

    /* On errors, check if the file already exists.  */
    ret = get_file_type_at (dirfd, &tmp_mode, false, file);
    if (ret == 0 && S_ISREG (tmp_mode))
      return 0;

    return crun_make_error (err, ret ? errno : saved_errno, "create file `%s`", file);
  }

Since I can only suggest a change to this specific line, my suggestion below assumes you've declared and assigned saved_errno earlier in the block.

      return crun_make_error (err, ret ? errno : saved_errno, "create file `%s`", file);

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Seems like a good advise. I'll check later.

@eriksjolund eriksjolund marked this pull request as draft March 13, 2026 06:58
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.

1 participant