Skip to content
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

zfs-2.1.16 patchset #16781

Open
wants to merge 5 commits into
base: zfs-2.1-release
Choose a base branch
from

Conversation

tonyhutter
Copy link
Contributor

Motivation and Context

Proposed patchset for zfs-2.1.16

Description

The EL 5.14.0-503.11.1.el9_5.x86_64 kernel broke the build. We need cfb96c7 and e3120f7 to get it building again.

How Has This Been Tested?

Test build only

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Performance enhancement (non-breaking change which improves efficiency)
  • Code cleanup (non-breaking change which makes code smaller or more readable)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
  • Documentation (a change to man pages or other documentation)

Checklist:

robn and others added 2 commits November 18, 2024 13:14
43e8f6e introduced a subtle API misuse, in that it passed the output
from vdev_bdev_mode() back into itself. Fortunately, the
SPA_MODE_(READ|WRITE) bit values exactly map to the FMODE_(READ|WRITE) &
BLK_OPEN_(READ|WRITE) bit values, so it didn't result in a bug, but it
was hard to read and understand, so I cleaned it up.

In doing so, I noticed that the only call to vdev_bdev_mode() without
the "exclusive" flag set was in that misuse, and actually, we never do a
non-exclusive blkdev_get_by_path(). So I've just made exclusive be
always-on.


Sponsored-by: Klara, Inc.
Sponsored-by: Wasabi Technology, Inc.
Reviewed by: Brian Behlendorf <[email protected]>
Reviewed-by: Allan Jude <[email protected]>
Signed-off-by: Rob Norris <[email protected]>
Closes openzfs#15995
bdev_open_by_path() is replaced by bdev_file_open_by_path(), which
returns a plain old struct file*. Release function is gone entirely; the
regular file release function fput() will take care of the bdev
specifics.

Reviewed-by: Tony Hutter <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Rob Norris <[email protected]>
Sponsored-by: https://despairlabs.com/sponsor/
Closes openzfs#16027
Closes openzfs#16033
@tonyhutter
Copy link
Contributor Author

I think this goes without saying, but zfs-2.1.16 will be for Almalinux 8-9 only (not Fedora).

Fix a build error on the github runner:

  Unpacking of 'zfs-2.1.16-1.x86_64.rpm' failed at
  /usr/share/perl5/Alien/Package/Rpm.pm line 168.

Signed-off-by: Tony Hutter <[email protected]>
META file and changelog updated.

Signed-off-by: Tony Hutter <[email protected]>
@tonyhutter tonyhutter force-pushed the zfs-2.1.16-hutter branch 6 times, most recently from 95e3d84 to 9a6cb8b Compare November 22, 2024 22:51
@Zerout
Copy link

Zerout commented Nov 26, 2024

I successfully compiled rpms from tonyhutter:zfs-2.1.16-hutter commit 9a6cb8b in a Rocky Linux 9.5 VM.

The rpms were then installed on both a Alma Linux 9.5 and RHEL 9.5 server and dkms succeded in compiling the kernel modules with the latest kernel that broke kernel module compiling of 2.1.15.

The final result is that things work exactly like before and personally even though I admit that running it for 24h is far from a reasonable timeframe I think that it's as stable as 2.1.15 was before the 9.5 kernel.

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