2019-06-30 11:39:13 -07:00
|
|
|
#include <sys/mount.h>
|
2020-04-01 04:39:28 -07:00
|
|
|
#include <sys/socket.h>
|
|
|
|
#include <sys/un.h>
|
2019-06-30 11:39:13 -07:00
|
|
|
#include <unistd.h>
|
2019-05-27 00:29:43 -07:00
|
|
|
#include <stdlib.h>
|
2019-11-19 00:16:20 -05:00
|
|
|
#include <vector>
|
2019-05-27 00:29:43 -07:00
|
|
|
|
2020-06-17 01:17:28 -07:00
|
|
|
#include <utils.hpp>
|
2019-12-13 06:05:12 -05:00
|
|
|
|
2019-05-27 00:29:43 -07:00
|
|
|
struct cmdline {
|
2019-12-06 12:02:34 -05:00
|
|
|
bool skip_initramfs;
|
Logical Resizable Android Partitions support
The way how logical partition, or "Logical Resizable Android Partitions"
as they say in AOSP source code, is setup makes it impossible to early
mount the partitions from the shared super partition with just
a few lines of code; in fact, AOSP has a whole "fs_mgr" folder which
consist of multiple complex libraries, with 15K lines of code just
to deal with the device mapper shenanigans.
In order to keep the already overly complicated MagiskInit more
managable, I chose NOT to go the route of including fs_mgr directly
into MagiskInit. Luckily, starting from Android Q, Google decided to
split init startup into 3 stages, with the first stage doing _only_
early mount. This is great news, because we can simply let the stock
init do its own thing for us, and we intercept the bootup sequence.
So the workflow can be visualized roughly below:
Magisk First Stage --> First Stage Mount --> Magisk Second Stage --+
(MagiskInit) (Original Init) (MagiskInit) +
+
+
...Rest of the boot... <-- Second Stage <-- Selinux Setup <--+
(__________________ Original Init ____________________)
The catch here is that after doing all the first stage mounting, /init
will pivot /system as root directory (/), leaving us impossible to
regain control after we hand it over. So the solution here is to patch
fstab in /first_stage_ramdisk on-the-fly to redirect /system to
/system_root, making the original init do all the hard work for
us and mount required early mount partitions, but skips the step of
switching root directory. It will also conveniently hand over execution
back to MagiskInit, which we will reuse the routine for patching
root directory in normal system-as-root situations.
2019-06-29 00:47:29 -07:00
|
|
|
bool force_normal_boot;
|
2019-05-27 00:29:43 -07:00
|
|
|
char slot[3];
|
2020-05-03 22:49:54 -07:00
|
|
|
char dt_dir[64];
|
|
|
|
char hardware[32];
|
|
|
|
char hardware_plat[32];
|
2019-05-27 00:29:43 -07:00
|
|
|
};
|
|
|
|
|
|
|
|
struct raw_data {
|
2019-07-16 01:08:28 -07:00
|
|
|
uint8_t *buf = nullptr;
|
|
|
|
size_t sz = 0;
|
|
|
|
|
|
|
|
raw_data() = default;
|
|
|
|
raw_data(const raw_data&) = delete;
|
|
|
|
raw_data(raw_data &&d) {
|
2019-07-16 23:30:54 -07:00
|
|
|
buf = d.buf;
|
|
|
|
sz = d.sz;
|
|
|
|
d.buf = nullptr;
|
|
|
|
d.sz = 0;
|
2019-07-16 01:08:28 -07:00
|
|
|
}
|
|
|
|
~raw_data() {
|
|
|
|
free(buf);
|
|
|
|
}
|
2019-05-27 00:29:43 -07:00
|
|
|
};
|
|
|
|
|
2020-05-03 22:49:54 -07:00
|
|
|
struct fstab_entry {
|
|
|
|
std::string dev;
|
|
|
|
std::string mnt_point;
|
|
|
|
std::string type;
|
|
|
|
std::string mnt_flags;
|
|
|
|
std::string fsmgr_flags;
|
|
|
|
|
|
|
|
fstab_entry() = default;
|
|
|
|
fstab_entry(const fstab_entry &o) = delete;
|
|
|
|
fstab_entry(fstab_entry &&o) = default;
|
Force init to load fstab from file in 2SI
Patching DTBs is proven to be difficult and problematic as there are
tons of different formats out there. Adding support for all the formats
in magiskboot has been quite an headache in the past year, and it still
definitely does not cover all possible cases of them out there.
There is another issue: fake dt fstabs. Some super old devices do not
have device trees in their boot images, so some custom ROM developers
had came up with a "genius" solution: hardcode fstab entries directly
in the kernel source code and create fake device tree nodes even if
Android 10+ init can graciously take fstab files instead (-_-) 。。。
And there is YET another issue: DTBs are not always in boot images!
Google is crazy enough to litter DTBs all over the place, it is like
they cannot make up their minds (duh). This means the dt fstabs can be
either concatnated after the kernel (1), in the DTB partition (2), in
the DTBO partition (3), in the recovery_dtbo section in boot images (4),
or in the dtb section in boot images (5). FIVE f**king places, how can
anyone keep up with that!
With Android 10+ that uses 2 stage inits, it is crutual for Magisk to
be able to modify fstab mount points in order to let the original init
mount partitions for us, but NOT switch root and continue booting. For
devices using dt for early mount fstab, we used to patch the DTB at
install time with magiskboot. However these changes are permanent and
cannot be restored back at reinstallation.
With this commit, Magisk will read dt fstabs and write them to ramdisk
at boot time. And in that case, the init binary will also be patched
to force it to NEVER use fstabs in device-tree. By doing so, we can
unify ramdisk based 2SI fstab patching as basically we are just patching
fstab files. This also means we can manipulate fstab whatever Magisk
needs in the future without the need to going through the headache that
is patching DTBs at installation.
2020-05-04 02:21:51 -07:00
|
|
|
void to_file(FILE *fp);
|
2020-05-03 22:49:54 -07:00
|
|
|
};
|
|
|
|
|
|
|
|
#define INIT_SOCKET "MAGISKINIT"
|
|
|
|
#define DEFAULT_DT_DIR "/proc/device-tree/firmware/android"
|
|
|
|
|
|
|
|
void load_kernel_info(cmdline *cmd);
|
|
|
|
int dump_magisk(const char *path, mode_t mode);
|
|
|
|
int magisk_proxy_main(int argc, char *argv[]);
|
|
|
|
void setup_klog();
|
|
|
|
void setup_tmp(const char *path, const raw_data &self, const raw_data &config);
|
|
|
|
|
|
|
|
using str_pairs = std::initializer_list<std::pair<std::string_view, std::string_view>>;
|
|
|
|
int raw_data_patch(void *addr, size_t sz, str_pairs list);
|
|
|
|
|
2020-04-19 04:56:56 -07:00
|
|
|
/***************
|
Logical Resizable Android Partitions support
The way how logical partition, or "Logical Resizable Android Partitions"
as they say in AOSP source code, is setup makes it impossible to early
mount the partitions from the shared super partition with just
a few lines of code; in fact, AOSP has a whole "fs_mgr" folder which
consist of multiple complex libraries, with 15K lines of code just
to deal with the device mapper shenanigans.
In order to keep the already overly complicated MagiskInit more
managable, I chose NOT to go the route of including fs_mgr directly
into MagiskInit. Luckily, starting from Android Q, Google decided to
split init startup into 3 stages, with the first stage doing _only_
early mount. This is great news, because we can simply let the stock
init do its own thing for us, and we intercept the bootup sequence.
So the workflow can be visualized roughly below:
Magisk First Stage --> First Stage Mount --> Magisk Second Stage --+
(MagiskInit) (Original Init) (MagiskInit) +
+
+
...Rest of the boot... <-- Second Stage <-- Selinux Setup <--+
(__________________ Original Init ____________________)
The catch here is that after doing all the first stage mounting, /init
will pivot /system as root directory (/), leaving us impossible to
regain control after we hand it over. So the solution here is to patch
fstab in /first_stage_ramdisk on-the-fly to redirect /system to
/system_root, making the original init do all the hard work for
us and mount required early mount partitions, but skips the step of
switching root directory. It will also conveniently hand over execution
back to MagiskInit, which we will reuse the routine for patching
root directory in normal system-as-root situations.
2019-06-29 00:47:29 -07:00
|
|
|
* Base classes
|
2020-04-19 04:56:56 -07:00
|
|
|
***************/
|
Logical Resizable Android Partitions support
The way how logical partition, or "Logical Resizable Android Partitions"
as they say in AOSP source code, is setup makes it impossible to early
mount the partitions from the shared super partition with just
a few lines of code; in fact, AOSP has a whole "fs_mgr" folder which
consist of multiple complex libraries, with 15K lines of code just
to deal with the device mapper shenanigans.
In order to keep the already overly complicated MagiskInit more
managable, I chose NOT to go the route of including fs_mgr directly
into MagiskInit. Luckily, starting from Android Q, Google decided to
split init startup into 3 stages, with the first stage doing _only_
early mount. This is great news, because we can simply let the stock
init do its own thing for us, and we intercept the bootup sequence.
So the workflow can be visualized roughly below:
Magisk First Stage --> First Stage Mount --> Magisk Second Stage --+
(MagiskInit) (Original Init) (MagiskInit) +
+
+
...Rest of the boot... <-- Second Stage <-- Selinux Setup <--+
(__________________ Original Init ____________________)
The catch here is that after doing all the first stage mounting, /init
will pivot /system as root directory (/), leaving us impossible to
regain control after we hand it over. So the solution here is to patch
fstab in /first_stage_ramdisk on-the-fly to redirect /system to
/system_root, making the original init do all the hard work for
us and mount required early mount partitions, but skips the step of
switching root directory. It will also conveniently hand over execution
back to MagiskInit, which we will reuse the routine for patching
root directory in normal system-as-root situations.
2019-06-29 00:47:29 -07:00
|
|
|
|
2019-06-16 12:45:32 -07:00
|
|
|
class BaseInit {
|
|
|
|
protected:
|
2019-06-15 22:25:09 -07:00
|
|
|
cmdline *cmd;
|
2019-05-27 00:29:43 -07:00
|
|
|
char **argv;
|
2019-11-19 00:16:20 -05:00
|
|
|
std::vector<std::string> mount_list;
|
Logical Resizable Android Partitions support
The way how logical partition, or "Logical Resizable Android Partitions"
as they say in AOSP source code, is setup makes it impossible to early
mount the partitions from the shared super partition with just
a few lines of code; in fact, AOSP has a whole "fs_mgr" folder which
consist of multiple complex libraries, with 15K lines of code just
to deal with the device mapper shenanigans.
In order to keep the already overly complicated MagiskInit more
managable, I chose NOT to go the route of including fs_mgr directly
into MagiskInit. Luckily, starting from Android Q, Google decided to
split init startup into 3 stages, with the first stage doing _only_
early mount. This is great news, because we can simply let the stock
init do its own thing for us, and we intercept the bootup sequence.
So the workflow can be visualized roughly below:
Magisk First Stage --> First Stage Mount --> Magisk Second Stage --+
(MagiskInit) (Original Init) (MagiskInit) +
+
+
...Rest of the boot... <-- Second Stage <-- Selinux Setup <--+
(__________________ Original Init ____________________)
The catch here is that after doing all the first stage mounting, /init
will pivot /system as root directory (/), leaving us impossible to
regain control after we hand it over. So the solution here is to patch
fstab in /first_stage_ramdisk on-the-fly to redirect /system to
/system_root, making the original init do all the hard work for
us and mount required early mount partitions, but skips the step of
switching root directory. It will also conveniently hand over execution
back to MagiskInit, which we will reuse the routine for patching
root directory in normal system-as-root situations.
2019-06-29 00:47:29 -07:00
|
|
|
|
2020-04-19 04:56:56 -07:00
|
|
|
void exec_init() {
|
2019-06-30 11:39:13 -07:00
|
|
|
cleanup();
|
2020-04-19 04:56:56 -07:00
|
|
|
execv("/init", argv);
|
2019-06-30 11:39:13 -07:00
|
|
|
exit(1);
|
|
|
|
}
|
2019-11-19 00:16:20 -05:00
|
|
|
virtual void cleanup();
|
2019-06-22 03:14:33 -07:00
|
|
|
public:
|
2019-11-19 00:16:20 -05:00
|
|
|
BaseInit(char *argv[], cmdline *cmd) :
|
2019-12-13 06:05:12 -05:00
|
|
|
cmd(cmd), argv(argv), mount_list{"/sys", "/proc"} {}
|
2019-06-22 03:14:33 -07:00
|
|
|
virtual ~BaseInit() = default;
|
|
|
|
virtual void start() = 0;
|
Force init to load fstab from file in 2SI
Patching DTBs is proven to be difficult and problematic as there are
tons of different formats out there. Adding support for all the formats
in magiskboot has been quite an headache in the past year, and it still
definitely does not cover all possible cases of them out there.
There is another issue: fake dt fstabs. Some super old devices do not
have device trees in their boot images, so some custom ROM developers
had came up with a "genius" solution: hardcode fstab entries directly
in the kernel source code and create fake device tree nodes even if
Android 10+ init can graciously take fstab files instead (-_-) 。。。
And there is YET another issue: DTBs are not always in boot images!
Google is crazy enough to litter DTBs all over the place, it is like
they cannot make up their minds (duh). This means the dt fstabs can be
either concatnated after the kernel (1), in the DTB partition (2), in
the DTBO partition (3), in the recovery_dtbo section in boot images (4),
or in the dtb section in boot images (5). FIVE f**king places, how can
anyone keep up with that!
With Android 10+ that uses 2 stage inits, it is crutual for Magisk to
be able to modify fstab mount points in order to let the original init
mount partitions for us, but NOT switch root and continue booting. For
devices using dt for early mount fstab, we used to patch the DTB at
install time with magiskboot. However these changes are permanent and
cannot be restored back at reinstallation.
With this commit, Magisk will read dt fstabs and write them to ramdisk
at boot time. And in that case, the init binary will also be patched
to force it to NEVER use fstabs in device-tree. By doing so, we can
unify ramdisk based 2SI fstab patching as basically we are just patching
fstab files. This also means we can manipulate fstab whatever Magisk
needs in the future without the need to going through the headache that
is patching DTBs at installation.
2020-05-04 02:21:51 -07:00
|
|
|
void read_dt_fstab(std::vector<fstab_entry> &fstab);
|
2020-05-03 22:49:54 -07:00
|
|
|
void dt_early_mount();
|
2019-06-22 03:14:33 -07:00
|
|
|
};
|
|
|
|
|
|
|
|
class MagiskInit : public BaseInit {
|
|
|
|
protected:
|
2019-07-16 01:08:28 -07:00
|
|
|
raw_data self;
|
2020-04-12 05:34:56 -07:00
|
|
|
std::string persist_dir;
|
2019-05-27 00:29:43 -07:00
|
|
|
|
2019-06-22 03:14:33 -07:00
|
|
|
virtual void early_mount() = 0;
|
2020-04-19 04:56:56 -07:00
|
|
|
bool patch_sepolicy(const char *file);
|
2019-05-27 00:29:43 -07:00
|
|
|
public:
|
2020-04-12 05:34:56 -07:00
|
|
|
MagiskInit(char *argv[], cmdline *cmd) : BaseInit(argv, cmd) {}
|
2019-06-23 15:14:47 -07:00
|
|
|
};
|
|
|
|
|
2019-09-22 05:20:51 -04:00
|
|
|
class SARBase : public MagiskInit {
|
2019-06-23 15:14:47 -07:00
|
|
|
protected:
|
2019-07-16 01:08:28 -07:00
|
|
|
raw_data config;
|
2020-04-01 04:39:28 -07:00
|
|
|
std::vector<raw_file> overlays;
|
2019-06-24 01:21:33 -07:00
|
|
|
|
2020-04-01 04:39:28 -07:00
|
|
|
void backup_files();
|
2019-06-24 01:21:33 -07:00
|
|
|
void patch_rootdir();
|
2020-04-01 04:39:28 -07:00
|
|
|
void mount_system_root();
|
2019-06-23 15:14:47 -07:00
|
|
|
public:
|
2020-04-12 05:34:56 -07:00
|
|
|
SARBase(char *argv[], cmdline *cmd) : MagiskInit(argv, cmd) {}
|
2019-06-30 11:39:13 -07:00
|
|
|
void start() override {
|
|
|
|
early_mount();
|
|
|
|
patch_rootdir();
|
|
|
|
exec_init();
|
|
|
|
}
|
2019-06-23 15:14:47 -07:00
|
|
|
};
|
|
|
|
|
2020-04-19 04:56:56 -07:00
|
|
|
/***************
|
2019-09-22 05:15:31 -04:00
|
|
|
* 2 Stage Init
|
2020-04-19 04:56:56 -07:00
|
|
|
***************/
|
2019-06-16 12:45:32 -07:00
|
|
|
|
2020-04-01 04:39:28 -07:00
|
|
|
class FirstStageInit : public BaseInit {
|
2019-12-12 03:25:48 -05:00
|
|
|
private:
|
2019-09-22 05:15:31 -04:00
|
|
|
void prepare();
|
Force init to load fstab from file in 2SI
Patching DTBs is proven to be difficult and problematic as there are
tons of different formats out there. Adding support for all the formats
in magiskboot has been quite an headache in the past year, and it still
definitely does not cover all possible cases of them out there.
There is another issue: fake dt fstabs. Some super old devices do not
have device trees in their boot images, so some custom ROM developers
had came up with a "genius" solution: hardcode fstab entries directly
in the kernel source code and create fake device tree nodes even if
Android 10+ init can graciously take fstab files instead (-_-) 。。。
And there is YET another issue: DTBs are not always in boot images!
Google is crazy enough to litter DTBs all over the place, it is like
they cannot make up their minds (duh). This means the dt fstabs can be
either concatnated after the kernel (1), in the DTB partition (2), in
the DTBO partition (3), in the recovery_dtbo section in boot images (4),
or in the dtb section in boot images (5). FIVE f**king places, how can
anyone keep up with that!
With Android 10+ that uses 2 stage inits, it is crutual for Magisk to
be able to modify fstab mount points in order to let the original init
mount partitions for us, but NOT switch root and continue booting. For
devices using dt for early mount fstab, we used to patch the DTB at
install time with magiskboot. However these changes are permanent and
cannot be restored back at reinstallation.
With this commit, Magisk will read dt fstabs and write them to ramdisk
at boot time. And in that case, the init binary will also be patched
to force it to NEVER use fstabs in device-tree. By doing so, we can
unify ramdisk based 2SI fstab patching as basically we are just patching
fstab files. This also means we can manipulate fstab whatever Magisk
needs in the future without the need to going through the headache that
is patching DTBs at installation.
2020-05-04 02:21:51 -07:00
|
|
|
|
2019-09-22 05:15:31 -04:00
|
|
|
public:
|
2020-04-12 05:34:56 -07:00
|
|
|
FirstStageInit(char *argv[], cmdline *cmd) : BaseInit(argv, cmd) {
|
|
|
|
LOGD("%s\n", __FUNCTION__);
|
|
|
|
};
|
2019-09-22 05:15:31 -04:00
|
|
|
void start() override {
|
|
|
|
prepare();
|
|
|
|
exec_init();
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
2020-04-01 04:39:28 -07:00
|
|
|
class SARFirstStageInit : public SARBase {
|
|
|
|
private:
|
2020-04-19 22:15:12 -07:00
|
|
|
void prepare();
|
2020-04-01 04:39:28 -07:00
|
|
|
protected:
|
|
|
|
void early_mount() override;
|
|
|
|
public:
|
2020-04-12 05:34:56 -07:00
|
|
|
SARFirstStageInit(char *argv[], cmdline *cmd) : SARBase(argv, cmd) {
|
|
|
|
LOGD("%s\n", __FUNCTION__);
|
|
|
|
};
|
2020-04-01 04:39:28 -07:00
|
|
|
void start() override {
|
|
|
|
early_mount();
|
2020-04-19 22:15:12 -07:00
|
|
|
prepare();
|
|
|
|
exec_init();
|
2020-04-01 04:39:28 -07:00
|
|
|
}
|
|
|
|
};
|
|
|
|
|
2019-09-22 05:20:51 -04:00
|
|
|
class SecondStageInit : public SARBase {
|
Logical Resizable Android Partitions support
The way how logical partition, or "Logical Resizable Android Partitions"
as they say in AOSP source code, is setup makes it impossible to early
mount the partitions from the shared super partition with just
a few lines of code; in fact, AOSP has a whole "fs_mgr" folder which
consist of multiple complex libraries, with 15K lines of code just
to deal with the device mapper shenanigans.
In order to keep the already overly complicated MagiskInit more
managable, I chose NOT to go the route of including fs_mgr directly
into MagiskInit. Luckily, starting from Android Q, Google decided to
split init startup into 3 stages, with the first stage doing _only_
early mount. This is great news, because we can simply let the stock
init do its own thing for us, and we intercept the bootup sequence.
So the workflow can be visualized roughly below:
Magisk First Stage --> First Stage Mount --> Magisk Second Stage --+
(MagiskInit) (Original Init) (MagiskInit) +
+
+
...Rest of the boot... <-- Second Stage <-- Selinux Setup <--+
(__________________ Original Init ____________________)
The catch here is that after doing all the first stage mounting, /init
will pivot /system as root directory (/), leaving us impossible to
regain control after we hand it over. So the solution here is to patch
fstab in /first_stage_ramdisk on-the-fly to redirect /system to
/system_root, making the original init do all the hard work for
us and mount required early mount partitions, but skips the step of
switching root directory. It will also conveniently hand over execution
back to MagiskInit, which we will reuse the routine for patching
root directory in normal system-as-root situations.
2019-06-29 00:47:29 -07:00
|
|
|
protected:
|
|
|
|
void early_mount() override;
|
|
|
|
void cleanup() override { /* Do not do any cleanup */ }
|
|
|
|
public:
|
2020-04-12 05:34:56 -07:00
|
|
|
SecondStageInit(char *argv[]) : SARBase(argv, nullptr) {
|
|
|
|
LOGD("%s\n", __FUNCTION__);
|
|
|
|
};
|
Logical Resizable Android Partitions support
The way how logical partition, or "Logical Resizable Android Partitions"
as they say in AOSP source code, is setup makes it impossible to early
mount the partitions from the shared super partition with just
a few lines of code; in fact, AOSP has a whole "fs_mgr" folder which
consist of multiple complex libraries, with 15K lines of code just
to deal with the device mapper shenanigans.
In order to keep the already overly complicated MagiskInit more
managable, I chose NOT to go the route of including fs_mgr directly
into MagiskInit. Luckily, starting from Android Q, Google decided to
split init startup into 3 stages, with the first stage doing _only_
early mount. This is great news, because we can simply let the stock
init do its own thing for us, and we intercept the bootup sequence.
So the workflow can be visualized roughly below:
Magisk First Stage --> First Stage Mount --> Magisk Second Stage --+
(MagiskInit) (Original Init) (MagiskInit) +
+
+
...Rest of the boot... <-- Second Stage <-- Selinux Setup <--+
(__________________ Original Init ____________________)
The catch here is that after doing all the first stage mounting, /init
will pivot /system as root directory (/), leaving us impossible to
regain control after we hand it over. So the solution here is to patch
fstab in /first_stage_ramdisk on-the-fly to redirect /system to
/system_root, making the original init do all the hard work for
us and mount required early mount partitions, but skips the step of
switching root directory. It will also conveniently hand over execution
back to MagiskInit, which we will reuse the routine for patching
root directory in normal system-as-root situations.
2019-06-29 00:47:29 -07:00
|
|
|
};
|
|
|
|
|
2020-04-19 04:56:56 -07:00
|
|
|
/*************
|
2019-09-22 05:15:31 -04:00
|
|
|
* Legacy SAR
|
2020-04-19 04:56:56 -07:00
|
|
|
*************/
|
Logical Resizable Android Partitions support
The way how logical partition, or "Logical Resizable Android Partitions"
as they say in AOSP source code, is setup makes it impossible to early
mount the partitions from the shared super partition with just
a few lines of code; in fact, AOSP has a whole "fs_mgr" folder which
consist of multiple complex libraries, with 15K lines of code just
to deal with the device mapper shenanigans.
In order to keep the already overly complicated MagiskInit more
managable, I chose NOT to go the route of including fs_mgr directly
into MagiskInit. Luckily, starting from Android Q, Google decided to
split init startup into 3 stages, with the first stage doing _only_
early mount. This is great news, because we can simply let the stock
init do its own thing for us, and we intercept the bootup sequence.
So the workflow can be visualized roughly below:
Magisk First Stage --> First Stage Mount --> Magisk Second Stage --+
(MagiskInit) (Original Init) (MagiskInit) +
+
+
...Rest of the boot... <-- Second Stage <-- Selinux Setup <--+
(__________________ Original Init ____________________)
The catch here is that after doing all the first stage mounting, /init
will pivot /system as root directory (/), leaving us impossible to
regain control after we hand it over. So the solution here is to patch
fstab in /first_stage_ramdisk on-the-fly to redirect /system to
/system_root, making the original init do all the hard work for
us and mount required early mount partitions, but skips the step of
switching root directory. It will also conveniently hand over execution
back to MagiskInit, which we will reuse the routine for patching
root directory in normal system-as-root situations.
2019-06-29 00:47:29 -07:00
|
|
|
|
2019-09-22 05:20:51 -04:00
|
|
|
class SARInit : public SARBase {
|
Logical Resizable Android Partitions support
The way how logical partition, or "Logical Resizable Android Partitions"
as they say in AOSP source code, is setup makes it impossible to early
mount the partitions from the shared super partition with just
a few lines of code; in fact, AOSP has a whole "fs_mgr" folder which
consist of multiple complex libraries, with 15K lines of code just
to deal with the device mapper shenanigans.
In order to keep the already overly complicated MagiskInit more
managable, I chose NOT to go the route of including fs_mgr directly
into MagiskInit. Luckily, starting from Android Q, Google decided to
split init startup into 3 stages, with the first stage doing _only_
early mount. This is great news, because we can simply let the stock
init do its own thing for us, and we intercept the bootup sequence.
So the workflow can be visualized roughly below:
Magisk First Stage --> First Stage Mount --> Magisk Second Stage --+
(MagiskInit) (Original Init) (MagiskInit) +
+
+
...Rest of the boot... <-- Second Stage <-- Selinux Setup <--+
(__________________ Original Init ____________________)
The catch here is that after doing all the first stage mounting, /init
will pivot /system as root directory (/), leaving us impossible to
regain control after we hand it over. So the solution here is to patch
fstab in /first_stage_ramdisk on-the-fly to redirect /system to
/system_root, making the original init do all the hard work for
us and mount required early mount partitions, but skips the step of
switching root directory. It will also conveniently hand over execution
back to MagiskInit, which we will reuse the routine for patching
root directory in normal system-as-root situations.
2019-06-29 00:47:29 -07:00
|
|
|
protected:
|
|
|
|
void early_mount() override;
|
|
|
|
public:
|
2020-04-12 05:34:56 -07:00
|
|
|
SARInit(char *argv[], cmdline *cmd) : SARBase(argv, cmd) {
|
|
|
|
LOGD("%s\n", __FUNCTION__);
|
|
|
|
};
|
Logical Resizable Android Partitions support
The way how logical partition, or "Logical Resizable Android Partitions"
as they say in AOSP source code, is setup makes it impossible to early
mount the partitions from the shared super partition with just
a few lines of code; in fact, AOSP has a whole "fs_mgr" folder which
consist of multiple complex libraries, with 15K lines of code just
to deal with the device mapper shenanigans.
In order to keep the already overly complicated MagiskInit more
managable, I chose NOT to go the route of including fs_mgr directly
into MagiskInit. Luckily, starting from Android Q, Google decided to
split init startup into 3 stages, with the first stage doing _only_
early mount. This is great news, because we can simply let the stock
init do its own thing for us, and we intercept the bootup sequence.
So the workflow can be visualized roughly below:
Magisk First Stage --> First Stage Mount --> Magisk Second Stage --+
(MagiskInit) (Original Init) (MagiskInit) +
+
+
...Rest of the boot... <-- Second Stage <-- Selinux Setup <--+
(__________________ Original Init ____________________)
The catch here is that after doing all the first stage mounting, /init
will pivot /system as root directory (/), leaving us impossible to
regain control after we hand it over. So the solution here is to patch
fstab in /first_stage_ramdisk on-the-fly to redirect /system to
/system_root, making the original init do all the hard work for
us and mount required early mount partitions, but skips the step of
switching root directory. It will also conveniently hand over execution
back to MagiskInit, which we will reuse the routine for patching
root directory in normal system-as-root situations.
2019-06-29 00:47:29 -07:00
|
|
|
};
|
|
|
|
|
2020-04-19 04:56:56 -07:00
|
|
|
/************
|
Logical Resizable Android Partitions support
The way how logical partition, or "Logical Resizable Android Partitions"
as they say in AOSP source code, is setup makes it impossible to early
mount the partitions from the shared super partition with just
a few lines of code; in fact, AOSP has a whole "fs_mgr" folder which
consist of multiple complex libraries, with 15K lines of code just
to deal with the device mapper shenanigans.
In order to keep the already overly complicated MagiskInit more
managable, I chose NOT to go the route of including fs_mgr directly
into MagiskInit. Luckily, starting from Android Q, Google decided to
split init startup into 3 stages, with the first stage doing _only_
early mount. This is great news, because we can simply let the stock
init do its own thing for us, and we intercept the bootup sequence.
So the workflow can be visualized roughly below:
Magisk First Stage --> First Stage Mount --> Magisk Second Stage --+
(MagiskInit) (Original Init) (MagiskInit) +
+
+
...Rest of the boot... <-- Second Stage <-- Selinux Setup <--+
(__________________ Original Init ____________________)
The catch here is that after doing all the first stage mounting, /init
will pivot /system as root directory (/), leaving us impossible to
regain control after we hand it over. So the solution here is to patch
fstab in /first_stage_ramdisk on-the-fly to redirect /system to
/system_root, making the original init do all the hard work for
us and mount required early mount partitions, but skips the step of
switching root directory. It will also conveniently hand over execution
back to MagiskInit, which we will reuse the routine for patching
root directory in normal system-as-root situations.
2019-06-29 00:47:29 -07:00
|
|
|
* Initramfs
|
2020-04-19 04:56:56 -07:00
|
|
|
************/
|
Logical Resizable Android Partitions support
The way how logical partition, or "Logical Resizable Android Partitions"
as they say in AOSP source code, is setup makes it impossible to early
mount the partitions from the shared super partition with just
a few lines of code; in fact, AOSP has a whole "fs_mgr" folder which
consist of multiple complex libraries, with 15K lines of code just
to deal with the device mapper shenanigans.
In order to keep the already overly complicated MagiskInit more
managable, I chose NOT to go the route of including fs_mgr directly
into MagiskInit. Luckily, starting from Android Q, Google decided to
split init startup into 3 stages, with the first stage doing _only_
early mount. This is great news, because we can simply let the stock
init do its own thing for us, and we intercept the bootup sequence.
So the workflow can be visualized roughly below:
Magisk First Stage --> First Stage Mount --> Magisk Second Stage --+
(MagiskInit) (Original Init) (MagiskInit) +
+
+
...Rest of the boot... <-- Second Stage <-- Selinux Setup <--+
(__________________ Original Init ____________________)
The catch here is that after doing all the first stage mounting, /init
will pivot /system as root directory (/), leaving us impossible to
regain control after we hand it over. So the solution here is to patch
fstab in /first_stage_ramdisk on-the-fly to redirect /system to
/system_root, making the original init do all the hard work for
us and mount required early mount partitions, but skips the step of
switching root directory. It will also conveniently hand over execution
back to MagiskInit, which we will reuse the routine for patching
root directory in normal system-as-root situations.
2019-06-29 00:47:29 -07:00
|
|
|
|
2019-12-12 03:25:48 -05:00
|
|
|
class RootFSInit : public MagiskInit {
|
|
|
|
private:
|
|
|
|
void setup_rootfs();
|
2019-06-16 12:45:32 -07:00
|
|
|
protected:
|
|
|
|
void early_mount() override;
|
|
|
|
public:
|
2019-12-13 06:05:12 -05:00
|
|
|
RootFSInit(char *argv[], cmdline *cmd) : MagiskInit(argv, cmd) {
|
2020-04-12 05:34:56 -07:00
|
|
|
LOGD("%s\n", __FUNCTION__);
|
2019-12-13 06:05:12 -05:00
|
|
|
}
|
2019-06-16 12:45:32 -07:00
|
|
|
|
2019-12-12 03:25:48 -05:00
|
|
|
void start() override {
|
|
|
|
early_mount();
|
|
|
|
setup_rootfs();
|
|
|
|
exec_init();
|
|
|
|
}
|
2019-05-27 00:29:43 -07:00
|
|
|
};
|