-
Notifications
You must be signed in to change notification settings - Fork 17
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
module build fails for 6.1.83+, 6.6.23+, 6.7.11+, 6.8.2+, 6.9+ #245
Comments
@anbe42 Thank you for reporting.
should be true. But we must to pay attention to supporting older kernels. It now supports 3.10 or later. There are a lot of version-code switch in the code and it is really bad. I want to sort it out to discontinue the support for really older version. By the way, the modification to dm_io needs version-code switch as well. Since they are backported to older kernel like 6.1, 6.6, 6.7 and 6.8. Other kernels like 6.2 isn't affected? If so, the switch will be very terrible. |
What about replacing all
(completely untested) |
Thank you. But is this really the best one? I want a more succinct solution because I hardly think that complicated version-switches are maintainable. What is the aim of the flag added to dm_io and the reason it is backported to those specific kernel versions? |
The corresponding change "dm io: Support IO priority" has been introduced in
v6.9-rc1 (6e5f0f6383b4896c7e9b943d84b136149d0f45e9)
and has been backported to
v6.8.2 (3d02f57794b56f8a04a21fdfb04f20a1c9f712a7)
v6.7.11 (4156ddd66b15ca409cd52dc7040c28c25143ce5a)
v6.6.23 (5cfcea64883486d79c695afdc502e32eb1b71587)
v6.1.83 (92b3c2437df8fe55a5c7816d9521b1fb7d0718b0)
The solution is probably to conditionally append ', IOPRIO_DEFAULT' as last parameter to the dm_io calls.
The text was updated successfully, but these errors were encountered: