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: Linux 5.6 compatibility #84303

Closed
wants to merge 1 commit into from

Conversation

emilazy
Copy link
Member

@emilazy emilazy commented Apr 5, 2020

Motivation for this change

I cherry-picked the Linux 5.6 compatibility patches from the latest OpenZFS master. This builds, boots, and passes tests for me with 5.6.2 (and the installer test exercises a pre-5.6 version). The backported patches are all quite simple, mostly dealing with the fallout of the 32-bit timepocalypse.

I've omitted openzfs/zfs@bd0d24e (openzfs/zfs#10072) because it depends on openzfs/zfs@066e825, which is a much more invasive change, and the PR message implies that it only breaks a non-NixOS-default kernel configuration, for a kernel version we don't ship as default/latest/testing, due to an upstream change that was an accident to begin with.

I initially wanted to bump zfsUnstable so that there'd be a pristine (albeit unreleased) upstream option for current kernels, but unfortunately the couple commits I checked broke the test with an ominous cannot mount 'rpool': Input/output error. In the spirit of procrastination, let's hope whatever that is goes away by the time of the next upstream release.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@emilazy emilazy force-pushed the zfs-linux-5.6-compat branch 2 times, most recently from 162f659 to d8ab465 Compare April 5, 2020 01:48
The only conflict that wasn't automatically resolved was an addition in
config/kernel.m4 with changed context.

I took a basic look over the cherry-picked patches and nothing seems
obviously incorrect.
@emilazy
Copy link
Member Author

emilazy commented Apr 5, 2020

@GrahamcOfBorg test zfs

@veprbl
Copy link
Member

veprbl commented Apr 8, 2020

@emilazy Does #84595 work for you?

@emilazy
Copy link
Member Author

emilazy commented Apr 8, 2020

Will try to test; the diff looks about the same to me, but I don't think grabbing a combined diff from a random gist is a great solution compared to the separated format-patches here; cc @Mic92.

@lukateras lukateras mentioned this pull request Apr 8, 2020
10 tasks
@Mic92
Copy link
Member

Mic92 commented Apr 8, 2020

I reviewed the patch before adding it.

@emilazy
Copy link
Member Author

emilazy commented Apr 9, 2020

Closing due to merge of substantially similar patch.

@Mic92 A ping so I can know that there's no need to keep a patch rebased against master and can drop it from my local tree would be appreciated in future.

@emilazy emilazy closed this Apr 9, 2020
@emilazy emilazy deleted the zfs-linux-5.6-compat branch May 8, 2020 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants