Skip to content

Conversation

@eriksjolund
Copy link
Contributor

No description provided.

@gemini-code-assist
Copy link

Summary of Changes

Hello @eriksjolund, 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 error handling logic within the libcrun library for Linux systems. It addresses a potential issue where the errno global variable could be inadvertently modified by subsequent function calls after an error occurred, leading to incorrect error reporting. The change ensures that the original error code is preserved for accurate debugging and logging.

Highlights

  • Error Handling: Ensures that the correct errno value is captured immediately after a potential failure when writing to /proc/sys/, preventing it from being overwritten by subsequent successful operations before being used for error reporting.

🧠 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/linux.c
    • Preserved errno value before subsequent function calls to ensure accurate error reporting in libcrun_set_sysctl.
Activity
  • The pull request was created by eriksjolund.
  • A single commit was made to address a specific error handling issue.
  • The change involves saving the errno value to a local variable immediately after a potential error to prevent its modification by subsequent operations.
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 correctly fixes a bug where errno could be clobbered by a function call before being used to report an error. The change saves errno to a local variable immediately after a failed write call, ensuring the correct error code is preserved and reported. I've added a minor suggestion for consistency, but the fix is solid.

eriksjolund added a commit to eriksjolund/crun that referenced this pull request Feb 7, 2026
Suggestion by gemini-code-assist in
containers#1993
was amended.

Signed-off-by: Erik Sjölund <erik.sjolund@gmail.com>
@eriksjolund eriksjolund force-pushed the linux-do-not-use-errno-after-success branch from 7073cb3 to 7fe104a Compare February 7, 2026 10:08
@packit-as-a-service
Copy link

TMT tests failed. @containers/packit-build please check.

@eriksjolund eriksjolund marked this pull request as draft February 7, 2026 14:44
@eriksjolund
Copy link
Contributor Author

I plan to do a small adjustment. (Probably tomorrow)

eriksjolund added a commit to eriksjolund/crun that referenced this pull request Feb 8, 2026
Suggestion by gemini-code-assist in
containers#1993
was amended.

Signed-off-by: Erik Sjölund <erik.sjolund@gmail.com>
@eriksjolund eriksjolund force-pushed the linux-do-not-use-errno-after-success branch from 7fe104a to d87dcb0 Compare February 8, 2026 07:57
@eriksjolund eriksjolund marked this pull request as ready for review February 8, 2026 08:19
Copy link
Collaborator

@kolyshkin kolyshkin left a comment

Choose a reason for hiding this comment

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

LGTM. Please rebase to pick some CI fixes so we can merge this.

Suggestion by gemini-code-assist in
containers#1993
was amended.

Signed-off-by: Erik Sjölund <erik.sjolund@gmail.com>
@eriksjolund eriksjolund force-pushed the linux-do-not-use-errno-after-success branch from d87dcb0 to 47c36ca Compare February 11, 2026 06:42
@eriksjolund
Copy link
Contributor Author

LGTM. Please rebase to pick some CI fixes so we can merge this.

Done

@kolyshkin kolyshkin merged commit 94fda0b into containers:main Feb 12, 2026
42 of 47 checks passed
@eriksjolund eriksjolund deleted the linux-do-not-use-errno-after-success branch February 12, 2026 09:46
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.

2 participants