-
-
Notifications
You must be signed in to change notification settings - Fork 2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
kernel: remove unused CONFIG guard becuase GKI kernel enable kprobe b…
…y default
- Loading branch information
Showing
4 changed files
with
0 additions
and
60 deletions.
There are no files selected for viewing
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
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
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
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
500ff9b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
KPROBES is enabled by default on GKI, but that doesn't mean all GKI kernels will have KPROBES. We're dealing with a kernel-based root solution here, it stands to reason that custom kernels will be involved, and some of them will have KPROBES disabled.
The guarding isn't doing any harm by existing, and covers edge cases such as monolithic builds of GKI kernels.
500ff9b
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just skip this commit. project authors are just trying to enforce standardization, which is a good thing.
manual hook users are not the norm.