…3113) (#1038)

The assumption that first app_process is zygote is fragile. Take the
following scernio into account:

1) User updates from KSU 1.0 to 3.0, with lsposed installed
2) User doesn't know how to install lkm via manager, find a friend to
patch init boot for him
3) Next boot, old ksud reports post-fs-data done with prctl, new kernel
doesn't know it, so throne tracker is not triggered
4) app_process logic gets triggered when lsposed executes lspd
5) Task work is bound to lspd's parent, which is a sh instead of init,
and it has already exited
6) User has no root

While this commit can fix it, it is strictly recommend that ksud version
should be greater than or equal to kernel version.

…3113) (KernelSU-Next#1038)

The assumption that first app_process is zygote is fragile. Take the
following scernio into account:

1) User updates from KSU 1.0 to 3.0, with lsposed installed
2) User doesn't know how to install lkm via manager, find a friend to
patch init boot for him
3) Next boot, old ksud reports post-fs-data done with prctl, new kernel
doesn't know it, so throne tracker is not triggered
4) app_process logic gets triggered when lsposed executes lspd
5) Task work is bound to lspd's parent, which is a sh instead of init,
and it has already exited
6) User has no root

While this commit can fix it, it is strictly recommend that ksud version
should be greater than or equal to kernel version.

…3113) (KernelSU-Next#1038)

The assumption that first app_process is zygote is fragile. Take the
following scernio into account:

1) User updates from KSU 1.0 to 3.0, with lsposed installed
2) User doesn't know how to install lkm via manager, find a friend to
patch init boot for him
3) Next boot, old ksud reports post-fs-data done with prctl, new kernel
doesn't know it, so throne tracker is not triggered
4) app_process logic gets triggered when lsposed executes lspd
5) Task work is bound to lspd's parent, which is a sh instead of init,
and it has already exited
6) User has no root

While this commit can fix it, it is strictly recommend that ksud version
should be greater than or equal to kernel version.

…3113) (#1038)

The assumption that first app_process is zygote is fragile. Take the
following scernio into account:

1) User updates from KSU 1.0 to 3.0, with lsposed installed
2) User doesn't know how to install lkm via manager, find a friend to
patch init boot for him
3) Next boot, old ksud reports post-fs-data done with prctl, new kernel
doesn't know it, so throne tracker is not triggered
4) app_process logic gets triggered when lsposed executes lspd
5) Task work is bound to lspd's parent, which is a sh instead of init,
and it has already exited
6) User has no root

While this commit can fix it, it is strictly recommend that ksud version
should be greater than or equal to kernel version.

…3113) (KernelSU-Next#1038)

The assumption that first app_process is zygote is fragile. Take the
following scernio into account:

1) User updates from KSU 1.0 to 3.0, with lsposed installed
2) User doesn't know how to install lkm via manager, find a friend to
patch init boot for him
3) Next boot, old ksud reports post-fs-data done with prctl, new kernel
doesn't know it, so throne tracker is not triggered
4) app_process logic gets triggered when lsposed executes lspd
5) Task work is bound to lspd's parent, which is a sh instead of init,
and it has already exited
6) User has no root

While this commit can fix it, it is strictly recommend that ksud version
should be greater than or equal to kernel version.

…3113) (KernelSU-Next#1038)

The assumption that first app_process is zygote is fragile. Take the
following scernio into account:

1) User updates from KSU 1.0 to 3.0, with lsposed installed
2) User doesn't know how to install lkm via manager, find a friend to
patch init boot for him
3) Next boot, old ksud reports post-fs-data done with prctl, new kernel
doesn't know it, so throne tracker is not triggered
4) app_process logic gets triggered when lsposed executes lspd
5) Task work is bound to lspd's parent, which is a sh instead of init,
and it has already exited
6) User has no root

While this commit can fix it, it is strictly recommend that ksud version
should be greater than or equal to kernel version.

…ernelSU#3113) (KernelSU-Next#1038)"

This reverts commit 21058f7.

…ernelSU#3113) (KernelSU-Next#1038)"

This reverts commit 21058f7.

…ernelSU#3113) (KernelSU-Next#1038)"

This reverts commit 21058f7.

…ernelSU#3113) (KernelSU-Next#1038)"

This reverts commit 21058f7.

…ernelSU#3113) (KernelSU-Next#1038)"

This reverts commit 21058f7.

…ernelSU#3113) (#1038)"

This reverts commit 21058f7.

…ernelSU#3113) (#1038)"

This reverts commit 21058f7.

…ernelSU#3113) (KernelSU-Next#1038)"

This reverts commit 21058f7.

…ernelSU#3113) (KernelSU-Next#1038)"

This reverts commit 21058f7.

…ernelSU#3113) (KernelSU-Next#1038)"

This reverts commit 21058f7.