Skip to content

dev-lang/go: Sync with Gentoo to fix segfault issue #2850

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 24, 2025

Conversation

chewi
Copy link
Contributor

@chewi chewi commented Apr 24, 2025

dev-lang/go: Sync with Gentoo to fix segfault issue

It's from Gentoo commit gentoo/gentoo@7158bcf. It fixes a nasty segfault issue affecting Docker and more.

How to use

Update Go, rebuild Docker, try it out.

Testing done

I've done the above on my Gentoo system and updated Go in the SDK. I don't think we need to run CI for this. It's already breaking anyway. Others have already reported success with the patch.

  • Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update) -- N/A because we haven't released the broken version
  • Inspected CI output for image differences: /boot and /usr size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc. -- N/A

It's from Gentoo commit 7158bcf1dca8775e2614ed826c69fa538dc79b86. It
fixes a nasty segfault issue affecting Docker and more.

Signed-off-by: James Le Cuirot <[email protected]>
@chewi chewi requested a review from a team April 24, 2025 16:30
@chewi chewi self-assigned this Apr 24, 2025
@chewi chewi changed the title dev-lang/go: Sync with Gentoo dev-lang/go: Sync with Gentoo to fix segfault issue Apr 24, 2025
@chewi chewi merged commit c4cca68 into main Apr 24, 2025
0 of 4 checks passed
@chewi chewi deleted the chewi/golang-segfault branch April 24, 2025 16:34
@jepio
Copy link
Member

jepio commented Apr 24, 2025

I've done the above on my Gentoo system and updated Go in the SDK. I don't think we need to run CI for this. It's already breaking anyway. Others have already reported success with the patch.

Better not skip the CI to catch potential regressions.

Copy link

Build action triggered: https://github.com/flatcar/scripts/actions/runs/14646818558

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.

3 participants