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: update to 2.1.2. #34563
zfs: update to 2.1.2. #34563
Conversation
Tested locally on x86_64 with root-on-ZFS. No issues with kernel 5.10.x, 5.14.x, 5.15.x. |
Ping @Vaelatern @ahesford |
Test failures on musl are because |
This is very brand new, only 2 hours. We prefer to wait at least a few days, so I'll ask that we put this on pause to see if upstream fixes musl. My zfs-on-root machine is in fact a musl box, so the musl failures obviously are relevant to me :) |
Yup, just getting the ball rolling. I'm dog-fooding it locally because I live the YOLO lifestyle. |
@Vaelatern fwiw this isn't inhibiting functionality, it's just a test for the mmap issues they had with file seeking. Disabling or fixing the tests should be equivalent, given that almost no one runs them :P I'm looking into the musl side to see if we can define the constants, otherwise I can open an issue with ZFS upstream. |
Even if the musl patch is accepted, the patch would need to be backported to our version indefinitely. Would it be better just to patch the tests here (or disable them)? Maybe defining these constants in make_build_args is sufficient... |
Fwiw the patch is likely to be accepted, from IRC discussion. I'm okay with backporting, and we can remove it when updating musl. |
I've pulled in openzfs/zfs#12891 - upstreams patch-of-choice for the |
LGTM, I can install on musl and reboot to test things. |
not opposed to backporting the zfs musl patch to fix this. |
Tested and seems to be working fine here. Thanks for the update! |
Testing the changes