Improve seccomp disable && Add locking to protect cred modifications in escape_to_root #2320
Conversation
This file contains hidden or 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
When disabling Seccomp, ensure that current->sighand->siglock is held during the operation. Signed-off-by: SsageParuders<[email protected]>
This commit introduces locking to ensure safe access and modification of the `cred` structure within the `escape_to_root` function. Signed-off-by: SsageParuders <[email protected]>"
SsageParuders
force-pushed
the
main
branch
2 times, most recently
from
eaea2b9 to
9d3666c
Compare
Ylarod
approved these changes
Dec 27, 2024
rsuntk
pushed a commit
to rsuntk/KernelSU
that referenced
this pull request
Dec 28, 2024
…in escape_to_root (tiann#2320) - When disabling Seccomp, ensure that current->sighand->siglock is held during the operation. - Locking to ensure safe access and modification of the `cred` structure within the `escape_to_root` function. --- I think this issue described in tiann#2236 may have been caused by concurrent read-write access without proper locking. --------- Signed-off-by: SsageParuders<[email protected]> Signed-off-by: SsageParuders <[email protected]>"
backslashxx
pushed a commit
to backslashxx/KernelSU
that referenced
this pull request
Dec 28, 2024
…in escape_to_root (tiann#2320) - When disabling Seccomp, ensure that current->sighand->siglock is held during the operation. - Locking to ensure safe access and modification of the `cred` structure within the `escape_to_root` function. --- I think this issue described in tiann#2236 may have been caused by concurrent read-write access without proper locking. --------- Signed-off-by: SsageParuders<[email protected]> Signed-off-by: SsageParuders <[email protected]>"
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Dec 28, 2024
Most kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. path_umount: backslashxx/mojito_krenol@2d51422 get_cred_rcu: introduced by tiann#2320 backport examples backslashxx/mojito_krenol@c1df3e5 backslashxx/msm8953-kernel@95903fb Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Dec 28, 2024
Most non-gki kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. path_umount: discussions: tiann#1464 example: backslashxx/mojito_krenol@2d51422 get_cred_rcu: introduced by tiann#2320 backport examples backslashxx/mojito_krenol@c1df3e5 backslashxx/msm8953-kernel@95903fb Signed-off-by: backslashxx <[email protected]>
|
for 3.18 / 4.x users that are self-maintaining their trees This should apply as is on < 4.19.303, < 4.14.334, and anything older, On upstreamed kernels, it will likely conflict, due to offending commit: recommendations: heres an example |
selfmusing
pushed a commit
to selfmusing/USlenreK
that referenced
this pull request
Dec 28, 2024
…in escape_to_root (tiann#2320) - When disabling Seccomp, ensure that current->sighand->siglock is held during the operation. - Locking to ensure safe access and modification of the `cred` structure within the `escape_to_root` function. --- I think this issue described in tiann#2236 may have been caused by concurrent read-write access without proper locking. --------- Signed-off-by: SsageParuders<[email protected]> Signed-off-by: SsageParuders <[email protected]>"
selfmusing
pushed a commit
to selfmusing/USlenreK
that referenced
this pull request
Dec 28, 2024
…in escape_to_root (tiann#2320) - When disabling Seccomp, ensure that current->sighand->siglock is held during the operation. - Locking to ensure safe access and modification of the `cred` structure within the `escape_to_root` function. --- I think this issue described in tiann#2236 may have been caused by concurrent read-write access without proper locking. --------- Signed-off-by: SsageParuders<[email protected]> Signed-off-by: SsageParuders <[email protected]>"
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Dec 28, 2024
Most non-gki kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. path_umount: discussions: tiann#1464 example: backslashxx/mojito_krenol@2d51422 get_cred_rcu: introduced by tiann#2320 backport examples backslashxx/mojito_krenol@c1df3e5 backslashxx/msm8953-kernel@95903fb Signed-off-by: backslashxx <[email protected]>
itejo443
pushed a commit
to itejo443/KernelSU
that referenced
this pull request
Dec 28, 2024
…in escape_to_root (tiann#2320) - When disabling Seccomp, ensure that current->sighand->siglock is held during the operation. - Locking to ensure safe access and modification of the `cred` structure within the `escape_to_root` function. --- I think this issue described in tiann#2236 may have been caused by concurrent read-write access without proper locking. --------- Signed-off-by: SsageParuders<[email protected]> Signed-off-by: SsageParuders <[email protected]>"
ananjaser1211
added a commit
to ananjaser1211/KernelSU
that referenced
this pull request
Dec 28, 2024
…cations in escape_to_root (tiann#2320)" This reverts commit 58ed786.
Jprimero15
pushed a commit
to Jprimero15/KernelSU
that referenced
this pull request
Dec 28, 2024
Most non-gki kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. path_umount: discussions: tiann#1464 example: backslashxx/mojito_krenol@2d51422 get_cred_rcu: introduced by tiann#2320 backport examples backslashxx/mojito_krenol@c1df3e5 backslashxx/msm8953-kernel@95903fb Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Dec 29, 2024
Most non-gki kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. path_umount: discussions: tiann#1464 example: backslashxx/mojito_krenol@2d51422 get_cred_rcu: introduced by tiann#2320 backport examples backslashxx/mojito_krenol@c1df3e5 backslashxx/msm8953-kernel@95903fb Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Dec 29, 2024
Most non-gki kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. path_umount: discussions: tiann#1464 example: backslashxx/mojito_krenol@2d51422 get_cred_rcu: introduced by tiann#2320 backport examples backslashxx/mojito_krenol@c1df3e5 backslashxx/msm8953-kernel@95903fb Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Dec 29, 2024
Most non-gki kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. path_umount: discussions: tiann#1464 example: backslashxx/mojito_krenol@2d51422 get_cred_rcu: introduced by tiann#2320 backport examples backslashxx/mojito_krenol@c1df3e5 backslashxx/msm8953-kernel@95903fb Signed-off-by: backslashxx <[email protected]>
rcmiku
pushed a commit
to rcmiku/KernelSU
that referenced
this pull request
Dec 29, 2024
…in escape_to_root (tiann#2320) - When disabling Seccomp, ensure that current->sighand->siglock is held during the operation. - Locking to ensure safe access and modification of the `cred` structure within the `escape_to_root` function. --- I think this issue described in tiann#2236 may have been caused by concurrent read-write access without proper locking. --------- Signed-off-by: SsageParuders<[email protected]> Signed-off-by: SsageParuders <[email protected]>"
rsuntk
pushed a commit
to rsuntk/KernelSU
that referenced
this pull request
Dec 29, 2024
…in escape_to_root (tiann#2320) - When disabling Seccomp, ensure that current->sighand->siglock is held during the operation. - Locking to ensure safe access and modification of the `cred` structure within the `escape_to_root` function. --- I think this issue described in tiann#2236 may have been caused by concurrent read-write access without proper locking. --------- Signed-off-by: SsageParuders<[email protected]> Signed-off-by: SsageParuders <[email protected]>"
rsuntk
added a commit
to rsuntk/KernelSU
that referenced
this pull request
Dec 29, 2024
tiann#2320 Signed-off-by: rsuntk <[email protected]>
MichaelPayne8
pushed a commit
to KrustyCook/KernelSU
that referenced
this pull request
Dec 29, 2024
…cations in escape_to_root (tiann#2320)" This reverts commit 58ed786. Signed-off-by: mrsrimar22 <[email protected]>
ananjaser1211
added a commit
to ananjaser1211/KernelSU
that referenced
this pull request
Dec 29, 2024
…d modifications in escape_to_root (tiann#2320)"" This reverts commit 3a7e9eb.
ananjaser1211
added a commit
to ananjaser1211/Apollo
that referenced
this pull request
Dec 29, 2024
* Backport get_cred_rcu for KSU * Refer to tiann/KernelSU#2320
sakana164
added a commit
to sakana164/KernelSU
that referenced
this pull request
Dec 30, 2024
…cations in escape_to_root (tiann#2320)" This reverts commit 58ed786.
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Dec 31, 2024
Most non-gki kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. path_umount: discussions: tiann#1464 example: backslashxx/mojito_krenol@2d51422 get_cred_rcu: introduced by tiann#2320 backport examples backslashxx/mojito_krenol@c1df3e5 backslashxx/msm8953-kernel@95903fb Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Dec 31, 2024
Most non-gki kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. path_umount: discussions: tiann#1464 example: backslashxx/mojito_krenol@2d51422 get_cred_rcu: introduced by tiann#2320 backport examples backslashxx/mojito_krenol@c1df3e5 backslashxx/msm8953-kernel@95903fb Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Dec 31, 2024
Most non-gki kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. path_umount: discussions: tiann#1464 example: backslashxx/mojito_krenol@2d51422 get_cred_rcu: introduced by tiann#2320 backport examples backslashxx/mojito_krenol@c1df3e5 backslashxx/msm8953-kernel@95903fb Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
May 25, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
May 25, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
May 25, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
May 25, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
May 25, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
May 27, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
May 28, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
May 28, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
May 31, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 1, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
Jun 1, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
Jun 4, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
Jun 6, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
Jun 6, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 8, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 9, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 9, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 9, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 9, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 9, 2025
It is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. The following are backportable: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 9, 2025
It is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. The following are backportable: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 10, 2025
It is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. The following are backportable: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 10, 2025
It is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. The following are backportable: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 10, 2025
It is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. The following are backportable: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 10, 2025
It is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. The following are backportable: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 11, 2025
It is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. The following are backportable: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
backslashxx
added a commit
to backslashxx/KernelSU
that referenced
this pull request
Jun 12, 2025
It is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. The following are backportable: - get_cred_rcu: context: tiann#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b - path_umount: context: tiann#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
Jun 14, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
Jun 14, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
Trijal08
pushed a commit
to Trijal08/KernelSU-Next
that referenced
this pull request
Jun 16, 2025
Legacy kernel builders have to touch their kernel source code anyway so we might as well tell them to backport things to achieve some sort of feature parity. As for others, it is a common thing on the scene to backport things, so this breaks kernel versioning assumptions. As for those, we scan and check kernel source. Required: - get_cred_rcu: context: tiann/KernelSU#2320 (comment) apply: torvalds/linux@97d0fb2 if above conflicts, try: xiaomi-sdm678/android_kernel_xiaomi_mojito@3fbad8b Optional: - path_umount: context: tiann/KernelSU#1464 (comment) apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@2d51422 - strncpy_from_user_nofault for 5.4, apply: torvalds/linux@bd88bb5 for 4.x, apply: xiaomi-sdm678/android_kernel_xiaomi_mojito@424e21f for any failures, check dependency chain of gregkh/linux@f43434e - kernel_read / kernel_write < 4.14, backport chain, tested on 4.9 torvalds/linux@e13ec93 torvalds/linux@bdd1d2d torvalds/linux@c41fbad torvalds/linux@ac452ac - hint, `curl $url.patch | git am` Signed-off-by: backslashxx <[email protected]>
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.
credstructure within theescape_to_rootfunction.I think this issue described in #2236 may have been caused by concurrent read-write access without proper locking.