-
-
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.
While it's understandable to disregard this, it's nonetheless a serious issue. I'm surprised the official repository would implement something like this. Enabling Kprobes by default is a security risk. Kprobes is generally discouraged due to security vulnerabilities, performance degradation, and its problematic nature.
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.
If you believe kprobe is problematic, discuss it with Google and Qualcomm. Every device with an official GKI kernel has kprobe enabled. Blaming and complaining are unproductive compared to submitting a PR.
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.
@0ctobot @TogoFire
actually kernelsu kprobe hooks are better, when I tried ridding off kprobe use on kernelsu,
I noticed that it hooks in a way less intrusive way than original manual hooks from the guide.
original manual hooks on the guide is so fucking intrusive and obsolete man.
nobody really got it up to what the kernelsu driver code can do.
it might be an interest to both of you
backslashxx#5
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.
It's not really a matter of what I think is better, or what I prefer, it's what I have to do as I maintain a monolithic 6.1 kernel which, while technically GKI, no longer functions as one and has no kernel module support and thus I couldn't use KPROBES even if I wanted to.
I get it, at that point, for all intents and purposes I'm non-GKI so fuck me. However, this is not the only scenario that one could reasonably envision KPROBES being disabled on a GKI kernel. So I just brought it up because I think it's a bit silly to operate under the assumption the KPROBES will always be enabled on GKI kernels. There is no drawback to having the guarding I'm place, and it covers edge cases.
I didn't anticipate that this was going to be received positively, but I thought I would mention it nonetheless.