Revert "zfs: unlock for 5.15"

[TredwellGit]

Motivation for this change

This reverts commit 86e057a.

Things done

• Fits CONTRIBUTING.md.

[jonringer]

After having my zfs partition borked from the SEEK_HOLE issue, I'm apprehensive about pushing the bounds of zfs. I would like to be more on the side of caution. Especially since data integrity is the first priority for anything.

[Mic92]

After having my zfs partition borked from the SEEK_HOLE issue, I'm apprehensive about pushing the bounds of zfs. I would like to be more on the side of caution. Especially since data integrity is the first priority for anything.

That was a zfs bug and not a compatibility issue: openzfs/zfs#11900

[jonringer]

After having my zfs partition borked from the SEEK_HOLE issue, I'm apprehensive about pushing the bounds of zfs. I would like to be more on the side of caution. Especially since data integrity is the first priority for anything.

That was a zfs bug and not a compatibility issue: openzfs/zfs#11900

Although I absolutely agree, it still makes me more risk adverse.

[jansol]

You win some, you lose some I guess.

This in combination with #147446 means that I woke up the other day to not getting a graphical login screen. Turns out that thanks to 5.14 being EOL I'm now stuck on 5.10, where amdgpu does not yet have any support for my card at all (RDNA2).

[Mic92]

Well. You can just apply Mic92@b31e0be
I used for some weeks now without issues.

[KenMacD]

@TredwellGit 2.1.2 is out, and lists 5.15 support 🥺

[TredwellGit]

#150923