support umount modules for 4.4 or higher Non-GKI kernel #1060
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
Bot-wxt1221
changed the title
|
I won't accept this PR because it may break many non gki kernel builds. |
|
I won't accept this PR because it may break many non gki kernel builds. |
|
Thank you, It works well on my 4.9 device. edit: |
CZB666-wdnmd
added a commit
to CZB666-wdnmd/KernelSU
that referenced
this pull request
Mar 10, 2024
tiann
pushed a commit
that referenced
this pull request
Mar 18, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 #955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d #1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 #1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a #1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/sdm845-419
that referenced
this pull request
Mar 19, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/sdm845-419
that referenced
this pull request
Mar 19, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/sdm845-419
that referenced
this pull request
Mar 19, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/sdm845-419
that referenced
this pull request
Mar 19, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
Danda420
pushed a commit
to Danda420/kernel_xiaomi_sm8250
that referenced
this pull request
Mar 22, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/sdm845-419
that referenced
this pull request
Mar 27, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/sdm845-419
that referenced
this pull request
May 23, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/sdm845-419
that referenced
this pull request
May 23, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/sdm845-419
that referenced
this pull request
May 25, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/sdm845-419
that referenced
this pull request
May 25, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Jun 6, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/sdm845-419
that referenced
this pull request
Jun 6, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Jun 8, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Jun 8, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Jun 8, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Jun 8, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Jun 8, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Jun 8, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Aug 10, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Aug 14, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Aug 18, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Aug 19, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Aug 21, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Aug 22, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Aug 26, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Sep 5, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Sep 5, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Sep 6, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Sep 6, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Sep 6, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Sep 7, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Sep 7, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Sep 9, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Sep 9, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Sep 11, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Sep 12, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Sep 17, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Sep 17, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Sep 17, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Sep 22, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Sep 22, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Sep 22, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Sep 22, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Oct 2, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Oct 15, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sm8250
that referenced
this pull request
Oct 16, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Oct 18, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[email protected]>
diphons
pushed a commit
to diphons/kernel_xiaomi_sdm845
that referenced
this pull request
Oct 24, 2024
Most kernel builders have to touch their kernel source code anyway, why not also tell them to backport path_umount so even non-gki users can benefit from this? I know this might be a bit controversial as this will raise the barrier of entry, but the benefits are just so high. Idea was from OnlyTomInSecond on KernelSU group chat way back, and it has been on the discussions for some time references: https://t.me/KernelSU_group/27237/176515 https://t.me/KernelSU_group/3249/184908 tiann/KernelSU#955 (comment) OnlyTomInSecond/android_kernel_xiaomi_sdm845@03d233d tiann/KernelSU#1060 https://elixir.bootlin.com/linux/v5.9.1/source/fs/namespace.c#L1728 https://elixir.bootlin.com/linux/v5.10.9/source/fs/namespace.c#L1730 https://elixir.bootlin.com/linux/v6.5/source/fs/namespace.c#L1887 tiann/KernelSU#1464 (comment) Kernel side change examples 5.4 natsumerinchan/kernel_oneplus_sm8350@961d978 4.19 backslashxx/android_karnol_ximi_fog@164917f 4.14 crdroidandroid/android_kernel_xiaomi_sm6150@c07c70a 4.9 backslashxx/msm8953-kernel@195f075 4.4 https://github.com/riarumoda/android_kernel_samsung_a9y18qlte/commit/21ea33fe41ce079ec1d663c0bd2201bc00a8084a tiann/KernelSU#1464 (comment) ofcourse having someone on 3.18 confirm this will be nice. **PROS**: umount modules for everyone **CONS**: barrier of entry +1 --------- Co-authored-by: Christoph Hellwig <[email protected]> Co-authored-by: Fede2782 <[email protected]> Co-authored-by: Tom <[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.
4.4内核及以上模块卸载。
只试过4.9，手上没设备了
To do:为了使用fs/namespace.c里面某些static函数，我把他们的static删了，参考这个commit（只关注fs/namespace.c）的更改，在我的一加6t内核中没有问题，有没有更优雅的方式呢