remove uneeded & broken set_fs()/get_fs() for kernel 5.10+ #345
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
also, this branch contains all commits needed for building against 5.10+ https://github.com/omegacoleman/rtl8812AU_8821AU_linux/tree/kernel-5.10 |
|
Thank you @omegacoleman for your efforts to get it working on a new kernel! I can confirm that I got your |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
using set_fs() and get_fs() to access the memory is long uneeded and finally removed in linux kernel 5.10 +, this PR fixes build against 5.10+ by cease this behavior with a macro,
RTW_NO_SET_FS. By default it is only enabled for 5.10+, but I recommend to define that any time as thisset_fs(KERNEL_DS)usage may cause severe security holes in some way.