-
Notifications
You must be signed in to change notification settings - Fork 100
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
drbd 9.2.7 fails to build against Linux 6.6.13 without spatch #84
Comments
Sorry for the long response on this. spatch-as-a-service is running fine. It may be that some combination of detected compat features causes compat-wise, we should be good for 6.7, but I will do some digging. |
@WanzenBug thanks for looking into this, we're building with Linux 6.6.x, it works fine with Linux 6.1.x, but started failing with update to Linux 6.6.x. We went through DRBD 9.2.6, 9.2.7 and 9.2.8 with this problem. Talos Linux follows Linux LTS releases, so we're on 6.6.x, not 6.7 |
Ok, I believe I have tracked down the issue:
So our patch system cannot the find the patch to apply when TLS is disabled on the kernel level, but it can find the A fix for that is already merged, but will have to wait for the next release. I did add a workaround in the SPAAS service, so requesting patches for 9.2.7 or 9.2.8 return the correct patches. So I believe you can try adding DRBD 9.2.8 again. On a related note: the only patches that need to be applied with the talos kernel are:
So I wonder if it would be possible to enable kTLS? |
Thanks for tracking this down!
We can look into that, my impression with kTLS was that it's more of a security issue itself as it's harder to patch in case of security problems. |
See LINBIT/drbd#84 (comment) Signed-off-by: Andrey Smirnov <[email protected]>
Thanks again, the build passed! |
Linux 6.6.x is the LTS kernel, but looks drbd release doesn't have proper cached patches:
Unfortunately, we don't have an option to get
spatch
into our build environment, so it'd the best if the required patch is cached.Is there any documented way to produce the patch and patch drbd source with it? Any other workarounds?
Also the patch-as-a-service seems to be down?
The text was updated successfully, but these errors were encountered: