Skip to content

Re-arm the OpenZFS kernel-compatibility gate for the main flavor #2

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.

Sign up for GitHub

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
Danathar merged 1 commit into from
Jul 27, 2026
Merged

Re-arm the OpenZFS kernel-compatibility gate for the main flavor #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 18 additions & 5 deletions images.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,13 +9,26 @@ zfs:
default:
minor_version: "2.4"
linux_experimental: false
# Fork customization: the Fedora `main` kernel (7.1.x on F44) is ahead of the
# maximum kernel OpenZFS 2.4.3 will configure against (7.0), so the ZFS akmod
# for this flavor needs --enable-linux-experimental the same way coreos-testing
# does. Without it `main` zfs builds fail at configure.
# Fork customization: `main` builds ZFS with upstream's kernel-compatibility
# gate ARMED (linux_experimental: false, same as the default).
#
# This was briefly `true`. zfs-aurora-complex used to build from
# `aurora-dx:latest`, whose Fedora `main` kernel (7.1.x on F44) runs ahead of
# the newest kernel OpenZFS 2.4.3 will configure against (7.0), so the akmod
# only built with --enable-linux-experimental. That consumer now builds from
# `aurora-dx:stable` (kernel 7.0.12-201.fc44), which is inside the supported
# range and needs no override.
#
# Leave this `false`. The flag disables OpenZFS's own refusal to build against
# an unvalidated kernel, so with it set, a future kernel bump past the
# supported ceiling would silently produce a module built against a kernel
# upstream declines to support instead of failing loudly. Failing the build is
# the wanted behaviour: consumers gate on it and surface it as an
# upstream-compat signal. Only set this `true` as a deliberate, temporary,
# documented exception -- never to make a red build go green.
main:
minor_version: "2.4"
linux_experimental: true
linux_experimental: false

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 27, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Update the stale fork-patch registry entry

Setting this to false retires the main-flavor experimental override, but FORK-PATCHES.md:83-105 still records zfs.main.linux_experimental: true as an active temporary patch and instructs maintainers to preserve it until OpenZFS supports the current main kernel. During the repository's documented upstream-merge process, that guidance can reintroduce the override this change deliberately removes; delete or revise T2 alongside this configuration change.

Useful? React with 👍 / 👎.

coreos-testing:
minor_version: "2.4"
linux_experimental: true
Expand Down
Loading