init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
/*
|
|
|
|
* Copyright (C) 2020 The Android Open Source Project
|
|
|
|
*
|
|
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
* you may not use this file except in compliance with the License.
|
|
|
|
* You may obtain a copy of the License at
|
|
|
|
*
|
|
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
*
|
|
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
* See the License for the specific language governing permissions and
|
|
|
|
* limitations under the License.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include "snapuserd_transition.h"
|
|
|
|
|
|
|
|
#include <sys/mman.h>
|
|
|
|
#include <sys/socket.h>
|
|
|
|
#include <sys/syscall.h>
|
|
|
|
#include <sys/xattr.h>
|
|
|
|
#include <unistd.h>
|
|
|
|
|
|
|
|
#include <filesystem>
|
|
|
|
#include <string>
|
2021-03-05 23:10:55 +01:00
|
|
|
#include <string_view>
|
2023-12-11 20:14:48 +01:00
|
|
|
#include <thread>
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
|
|
|
|
#include <android-base/file.h>
|
|
|
|
#include <android-base/logging.h>
|
|
|
|
#include <android-base/parseint.h>
|
2022-06-02 10:00:39 +02:00
|
|
|
#include <android-base/stringprintf.h>
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
#include <android-base/strings.h>
|
|
|
|
#include <android-base/unique_fd.h>
|
|
|
|
#include <cutils/sockets.h>
|
2022-01-25 08:05:31 +01:00
|
|
|
#include <fs_avb/fs_avb.h>
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
#include <libsnapshot/snapshot.h>
|
|
|
|
#include <private/android_filesystem_config.h>
|
2021-03-05 23:10:55 +01:00
|
|
|
#include <procinfo/process_map.h>
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
#include <selinux/android.h>
|
2021-07-26 08:59:18 +02:00
|
|
|
#include <snapuserd/snapuserd_client.h>
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
|
|
|
|
#include "block_dev_initializer.h"
|
2022-06-02 10:00:39 +02:00
|
|
|
#include "lmkd_service.h"
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
#include "service_utils.h"
|
|
|
|
#include "util.h"
|
|
|
|
|
|
|
|
namespace android {
|
|
|
|
namespace init {
|
|
|
|
|
|
|
|
using namespace std::string_literals;
|
|
|
|
|
|
|
|
using android::base::unique_fd;
|
|
|
|
using android::snapshot::SnapshotManager;
|
|
|
|
using android::snapshot::SnapuserdClient;
|
|
|
|
|
|
|
|
static constexpr char kSnapuserdPath[] = "/system/bin/snapuserd";
|
|
|
|
static constexpr char kSnapuserdFirstStagePidVar[] = "FIRST_STAGE_SNAPUSERD_PID";
|
|
|
|
static constexpr char kSnapuserdFirstStageFdVar[] = "FIRST_STAGE_SNAPUSERD_FD";
|
2021-07-22 06:53:28 +02:00
|
|
|
static constexpr char kSnapuserdFirstStageInfoVar[] = "FIRST_STAGE_SNAPUSERD_INFO";
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
static constexpr char kSnapuserdLabel[] = "u:object_r:snapuserd_exec:s0";
|
|
|
|
static constexpr char kSnapuserdSocketLabel[] = "u:object_r:snapuserd_socket:s0";
|
|
|
|
|
2024-03-28 17:51:52 +01:00
|
|
|
void LaunchFirstStageSnapuserd() {
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
SocketDescriptor socket_desc;
|
|
|
|
socket_desc.name = android::snapshot::kSnapuserdSocket;
|
|
|
|
socket_desc.type = SOCK_STREAM;
|
|
|
|
socket_desc.perm = 0660;
|
|
|
|
socket_desc.uid = AID_SYSTEM;
|
|
|
|
socket_desc.gid = AID_SYSTEM;
|
|
|
|
|
|
|
|
// We specify a label here even though it technically is not needed. During
|
|
|
|
// first_stage_mount there is no sepolicy loaded. Once sepolicy is loaded,
|
|
|
|
// we bypass the socket entirely.
|
|
|
|
auto socket = socket_desc.Create(kSnapuserdSocketLabel);
|
|
|
|
if (!socket.ok()) {
|
|
|
|
LOG(FATAL) << "Could not create snapuserd socket: " << socket.error();
|
|
|
|
}
|
|
|
|
|
|
|
|
pid_t pid = fork();
|
|
|
|
if (pid < 0) {
|
|
|
|
PLOG(FATAL) << "Cannot launch snapuserd; fork failed";
|
|
|
|
}
|
|
|
|
if (pid == 0) {
|
|
|
|
socket->Publish();
|
2021-10-03 11:41:13 +02:00
|
|
|
|
2024-03-28 17:51:52 +01:00
|
|
|
char arg0[] = "/system/bin/snapuserd";
|
|
|
|
char arg1[] = "-user_snapshot";
|
|
|
|
char* const argv[] = {arg0, arg1, nullptr};
|
|
|
|
if (execv(arg0, argv) < 0) {
|
|
|
|
PLOG(FATAL) << "Cannot launch snapuserd; execv failed";
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
}
|
2024-03-28 17:51:52 +01:00
|
|
|
_exit(127);
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
}
|
|
|
|
|
2021-07-22 06:53:28 +02:00
|
|
|
auto client = SnapuserdClient::Connect(android::snapshot::kSnapuserdSocket, 10s);
|
|
|
|
if (!client) {
|
|
|
|
LOG(FATAL) << "Could not connect to first-stage snapuserd";
|
|
|
|
}
|
|
|
|
if (client->SupportsSecondStageSocketHandoff()) {
|
|
|
|
setenv(kSnapuserdFirstStageInfoVar, "socket", 1);
|
|
|
|
}
|
|
|
|
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
setenv(kSnapuserdFirstStagePidVar, std::to_string(pid).c_str(), 1);
|
|
|
|
|
2023-01-03 06:11:13 +01:00
|
|
|
if (!client->RemoveTransitionedDaemonIndicator()) {
|
|
|
|
LOG(ERROR) << "RemoveTransitionedDaemonIndicator failed";
|
|
|
|
}
|
|
|
|
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
LOG(INFO) << "Relaunched snapuserd with pid: " << pid;
|
|
|
|
}
|
|
|
|
|
|
|
|
std::optional<pid_t> GetSnapuserdFirstStagePid() {
|
|
|
|
const char* pid_str = getenv(kSnapuserdFirstStagePidVar);
|
|
|
|
if (!pid_str) {
|
|
|
|
return {};
|
|
|
|
}
|
|
|
|
|
|
|
|
int pid = 0;
|
|
|
|
if (!android::base::ParseInt(pid_str, &pid)) {
|
|
|
|
LOG(FATAL) << "Could not parse pid in environment, " << kSnapuserdFirstStagePidVar << "="
|
|
|
|
<< pid_str;
|
|
|
|
}
|
|
|
|
return {pid};
|
|
|
|
}
|
|
|
|
|
|
|
|
static void RelabelLink(const std::string& link) {
|
|
|
|
selinux_android_restorecon(link.c_str(), 0);
|
|
|
|
|
|
|
|
std::string path;
|
|
|
|
if (android::base::Readlink(link, &path)) {
|
|
|
|
selinux_android_restorecon(path.c_str(), 0);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static void RelabelDeviceMapper() {
|
|
|
|
selinux_android_restorecon("/dev/device-mapper", 0);
|
|
|
|
|
|
|
|
std::error_code ec;
|
|
|
|
for (auto& iter : std::filesystem::directory_iterator("/dev/block", ec)) {
|
|
|
|
const auto& path = iter.path();
|
|
|
|
if (android::base::StartsWith(path.string(), "/dev/block/dm-")) {
|
|
|
|
selinux_android_restorecon(path.string().c_str(), 0);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static std::optional<int> GetRamdiskSnapuserdFd() {
|
|
|
|
const char* fd_str = getenv(kSnapuserdFirstStageFdVar);
|
|
|
|
if (!fd_str) {
|
|
|
|
return {};
|
|
|
|
}
|
|
|
|
|
|
|
|
int fd;
|
|
|
|
if (!android::base::ParseInt(fd_str, &fd)) {
|
|
|
|
LOG(FATAL) << "Could not parse fd in environment, " << kSnapuserdFirstStageFdVar << "="
|
|
|
|
<< fd_str;
|
|
|
|
}
|
|
|
|
return {fd};
|
|
|
|
}
|
|
|
|
|
|
|
|
void RestoreconRamdiskSnapuserd(int fd) {
|
|
|
|
if (fsetxattr(fd, XATTR_NAME_SELINUX, kSnapuserdLabel, strlen(kSnapuserdLabel) + 1, 0) < 0) {
|
|
|
|
PLOG(FATAL) << "fsetxattr snapuserd failed";
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
SnapuserdSelinuxHelper::SnapuserdSelinuxHelper(std::unique_ptr<SnapshotManager>&& sm, pid_t old_pid)
|
|
|
|
: sm_(std::move(sm)), old_pid_(old_pid) {
|
|
|
|
// Only dm-user device names change during transitions, so the other
|
|
|
|
// devices are expected to be present.
|
|
|
|
sm_->SetUeventRegenCallback([this](const std::string& device) -> bool {
|
|
|
|
if (android::base::StartsWith(device, "/dev/dm-user/")) {
|
|
|
|
return block_dev_init_.InitDmUser(android::base::Basename(device));
|
|
|
|
}
|
|
|
|
return true;
|
|
|
|
});
|
|
|
|
}
|
|
|
|
|
2021-03-05 23:10:55 +01:00
|
|
|
static void LockAllSystemPages() {
|
|
|
|
bool ok = true;
|
|
|
|
auto callback = [&](const android::procinfo::MapInfo& map) -> void {
|
|
|
|
if (!ok || android::base::StartsWith(map.name, "/dev/") ||
|
|
|
|
!android::base::StartsWith(map.name, "/")) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
auto start = reinterpret_cast<const void*>(map.start);
|
2024-02-15 02:03:01 +01:00
|
|
|
uint64_t len = android::procinfo::MappedFileSize(map);
|
2021-03-05 23:10:55 +01:00
|
|
|
if (!len) {
|
|
|
|
return;
|
|
|
|
}
|
2024-02-15 02:03:01 +01:00
|
|
|
|
2021-03-05 23:10:55 +01:00
|
|
|
if (mlock(start, len) < 0) {
|
2024-02-15 02:03:01 +01:00
|
|
|
PLOG(ERROR) << "\"" << map.name << "\": mlock(" << start << ", " << len
|
|
|
|
<< ") failed: pgoff = " << map.pgoff;
|
2021-03-05 23:10:55 +01:00
|
|
|
ok = false;
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
if (!android::procinfo::ReadProcessMaps(getpid(), callback) || !ok) {
|
2024-02-15 02:03:01 +01:00
|
|
|
LOG(FATAL) << "Could not process /proc/" << getpid() << "/maps file for init";
|
2021-03-05 23:10:55 +01:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
void SnapuserdSelinuxHelper::StartTransition() {
|
|
|
|
LOG(INFO) << "Starting SELinux transition of snapuserd";
|
|
|
|
|
|
|
|
// The restorecon path reads from /system etc, so make sure any reads have
|
|
|
|
// been cached before proceeding.
|
|
|
|
auto handle = selinux_android_file_context_handle();
|
|
|
|
if (!handle) {
|
|
|
|
LOG(FATAL) << "Could not create SELinux file context handle";
|
|
|
|
}
|
|
|
|
selinux_android_set_sehandle(handle);
|
|
|
|
|
|
|
|
// We cannot access /system after the transition, so make sure init is
|
|
|
|
// pinned in memory.
|
2021-03-05 23:10:55 +01:00
|
|
|
LockAllSystemPages();
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
|
|
|
|
argv_.emplace_back("snapuserd");
|
|
|
|
argv_.emplace_back("-no_socket");
|
2022-07-15 20:40:07 +02:00
|
|
|
if (!sm_->PrepareSnapuserdArgsForSelinux(&argv_)) {
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
LOG(FATAL) << "Could not perform selinux transition";
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void SnapuserdSelinuxHelper::FinishTransition() {
|
|
|
|
RelabelLink("/dev/block/by-name/super");
|
|
|
|
RelabelDeviceMapper();
|
|
|
|
|
|
|
|
selinux_android_restorecon("/dev/null", 0);
|
|
|
|
selinux_android_restorecon("/dev/urandom", 0);
|
|
|
|
selinux_android_restorecon("/dev/kmsg", 0);
|
|
|
|
selinux_android_restorecon("/dev/dm-user", SELINUX_ANDROID_RESTORECON_RECURSE);
|
|
|
|
|
|
|
|
RelaunchFirstStageSnapuserd();
|
|
|
|
|
|
|
|
if (munlockall() < 0) {
|
|
|
|
PLOG(ERROR) << "munlockall failed";
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2022-01-25 08:05:31 +01:00
|
|
|
/*
|
|
|
|
* Before starting init second stage, we will wait
|
|
|
|
* for snapuserd daemon to be up and running; bionic libc
|
|
|
|
* may read /system/etc/selinux/plat_property_contexts file
|
|
|
|
* before invoking main() function. This will happen if
|
|
|
|
* init initializes property during second stage. Any access
|
|
|
|
* to /system without snapuserd daemon will lead to a deadlock.
|
|
|
|
*
|
|
|
|
* Thus, we do a simple probe by reading system partition. This
|
|
|
|
* read will eventually be serviced by daemon confirming that
|
|
|
|
* daemon is up and running. Furthermore, we are still in the kernel
|
|
|
|
* domain and sepolicy has not been enforced yet. Thus, access
|
|
|
|
* to these device mapper block devices are ok even though
|
|
|
|
* we may see audit logs.
|
|
|
|
*/
|
|
|
|
bool SnapuserdSelinuxHelper::TestSnapuserdIsReady() {
|
2023-01-03 06:11:13 +01:00
|
|
|
// Wait for the daemon to be fully up. Daemon will write to path
|
|
|
|
// /metadata/ota/daemon-alive-indicator only when all the threads
|
|
|
|
// are ready and attached to dm-user.
|
|
|
|
//
|
|
|
|
// This check will fail for GRF devices with vendor on Android S.
|
|
|
|
// snapuserd binary from Android S won't be able to communicate
|
|
|
|
// and hence, we will fallback and issue I/O to verify
|
|
|
|
// the presence of daemon.
|
|
|
|
auto client = std::make_unique<SnapuserdClient>();
|
|
|
|
if (!client->IsTransitionedDaemonReady()) {
|
|
|
|
LOG(ERROR) << "IsTransitionedDaemonReady failed";
|
|
|
|
}
|
|
|
|
|
2022-01-25 08:05:31 +01:00
|
|
|
std::string dev = "/dev/block/mapper/system"s + fs_mgr_get_slot_suffix();
|
|
|
|
android::base::unique_fd fd(open(dev.c_str(), O_RDONLY | O_DIRECT));
|
|
|
|
if (fd < 0) {
|
|
|
|
PLOG(ERROR) << "open " << dev << " failed";
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
void* addr;
|
|
|
|
ssize_t page_size = getpagesize();
|
|
|
|
if (posix_memalign(&addr, page_size, page_size) < 0) {
|
|
|
|
PLOG(ERROR) << "posix_memalign with page size " << page_size;
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
std::unique_ptr<void, decltype(&::free)> buffer(addr, ::free);
|
|
|
|
|
|
|
|
int iter = 0;
|
|
|
|
while (iter < 10) {
|
|
|
|
ssize_t n = TEMP_FAILURE_RETRY(pread(fd.get(), buffer.get(), page_size, 0));
|
|
|
|
if (n < 0) {
|
|
|
|
// Wait for sometime before retry
|
|
|
|
std::this_thread::sleep_for(100ms);
|
|
|
|
} else if (n == page_size) {
|
|
|
|
return true;
|
|
|
|
} else {
|
|
|
|
LOG(ERROR) << "pread returned: " << n << " from: " << dev << " expected: " << page_size;
|
|
|
|
}
|
|
|
|
|
|
|
|
iter += 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
void SnapuserdSelinuxHelper::RelaunchFirstStageSnapuserd() {
|
2022-07-15 20:40:07 +02:00
|
|
|
if (!sm_->DetachFirstStageSnapuserdForSelinux()) {
|
|
|
|
LOG(FATAL) << "Could not perform selinux transition";
|
|
|
|
}
|
|
|
|
|
|
|
|
KillFirstStageSnapuserd(old_pid_);
|
|
|
|
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
auto fd = GetRamdiskSnapuserdFd();
|
|
|
|
if (!fd) {
|
|
|
|
LOG(FATAL) << "Environment variable " << kSnapuserdFirstStageFdVar << " was not set!";
|
|
|
|
}
|
|
|
|
unsetenv(kSnapuserdFirstStageFdVar);
|
|
|
|
|
|
|
|
RestoreconRamdiskSnapuserd(fd.value());
|
|
|
|
|
|
|
|
pid_t pid = fork();
|
|
|
|
if (pid < 0) {
|
|
|
|
PLOG(FATAL) << "Fork to relaunch snapuserd failed";
|
|
|
|
}
|
|
|
|
if (pid > 0) {
|
|
|
|
// We don't need the descriptor anymore, and it should be closed to
|
|
|
|
// avoid leaking into subprocesses.
|
|
|
|
close(fd.value());
|
|
|
|
|
|
|
|
setenv(kSnapuserdFirstStagePidVar, std::to_string(pid).c_str(), 1);
|
|
|
|
|
|
|
|
LOG(INFO) << "Relaunched snapuserd with pid: " << pid;
|
2022-01-25 08:05:31 +01:00
|
|
|
|
2022-06-02 10:00:39 +02:00
|
|
|
// Since daemon is not started as a service, we have
|
|
|
|
// to explicitly set the OOM score to default which is unkillable
|
|
|
|
std::string oom_str = std::to_string(DEFAULT_OOM_SCORE_ADJUST);
|
|
|
|
std::string oom_file = android::base::StringPrintf("/proc/%d/oom_score_adj", pid);
|
|
|
|
if (!android::base::WriteStringToFile(oom_str, oom_file)) {
|
|
|
|
PLOG(ERROR) << "couldn't write oom_score_adj to snapuserd daemon with pid: " << pid;
|
|
|
|
}
|
|
|
|
|
2022-01-25 08:05:31 +01:00
|
|
|
if (!TestSnapuserdIsReady()) {
|
|
|
|
PLOG(FATAL) << "snapuserd daemon failed to launch";
|
|
|
|
} else {
|
|
|
|
LOG(INFO) << "snapuserd daemon is up and running";
|
|
|
|
}
|
|
|
|
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Make sure the descriptor is gone after we exec.
|
|
|
|
if (fcntl(fd.value(), F_SETFD, FD_CLOEXEC) < 0) {
|
|
|
|
PLOG(FATAL) << "fcntl FD_CLOEXEC failed for snapuserd fd";
|
|
|
|
}
|
|
|
|
|
|
|
|
std::vector<char*> argv;
|
|
|
|
for (auto& arg : argv_) {
|
|
|
|
argv.emplace_back(arg.data());
|
|
|
|
}
|
|
|
|
argv.emplace_back(nullptr);
|
|
|
|
|
|
|
|
int rv = syscall(SYS_execveat, fd.value(), "", reinterpret_cast<char* const*>(argv.data()),
|
|
|
|
nullptr, AT_EMPTY_PATH);
|
|
|
|
if (rv < 0) {
|
|
|
|
PLOG(FATAL) << "Failed to execveat() snapuserd";
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
std::unique_ptr<SnapuserdSelinuxHelper> SnapuserdSelinuxHelper::CreateIfNeeded() {
|
|
|
|
if (IsRecoveryMode()) {
|
|
|
|
return nullptr;
|
|
|
|
}
|
|
|
|
|
|
|
|
auto old_pid = GetSnapuserdFirstStagePid();
|
|
|
|
if (!old_pid) {
|
|
|
|
return nullptr;
|
|
|
|
}
|
|
|
|
|
|
|
|
auto sm = SnapshotManager::NewForFirstStageMount();
|
|
|
|
if (!sm) {
|
|
|
|
LOG(FATAL) << "Unable to create SnapshotManager";
|
|
|
|
}
|
|
|
|
return std::make_unique<SnapuserdSelinuxHelper>(std::move(sm), old_pid.value());
|
|
|
|
}
|
|
|
|
|
|
|
|
void KillFirstStageSnapuserd(pid_t pid) {
|
|
|
|
if (kill(pid, SIGTERM) < 0 && errno != ESRCH) {
|
|
|
|
LOG(ERROR) << "Kill snapuserd pid failed: " << pid;
|
|
|
|
} else {
|
|
|
|
LOG(INFO) << "Sent SIGTERM to snapuserd process " << pid;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void CleanupSnapuserdSocket() {
|
|
|
|
auto socket_path = ANDROID_SOCKET_DIR "/"s + android::snapshot::kSnapuserdSocket;
|
|
|
|
if (access(socket_path.c_str(), F_OK) != 0) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Tell the daemon to stop accepting connections and to gracefully exit
|
|
|
|
// once all outstanding handlers have terminated.
|
|
|
|
if (auto client = SnapuserdClient::Connect(android::snapshot::kSnapuserdSocket, 3s)) {
|
|
|
|
client->DetachSnapuserd();
|
|
|
|
}
|
|
|
|
|
|
|
|
// Unlink the socket so we can create it again in second-stage.
|
|
|
|
if (unlink(socket_path.c_str()) < 0) {
|
|
|
|
PLOG(FATAL) << "unlink " << socket_path << " failed";
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void SaveRamdiskPathToSnapuserd() {
|
|
|
|
int fd = open(kSnapuserdPath, O_PATH);
|
|
|
|
if (fd < 0) {
|
|
|
|
PLOG(FATAL) << "Unable to open snapuserd: " << kSnapuserdPath;
|
|
|
|
}
|
|
|
|
|
|
|
|
auto value = std::to_string(fd);
|
|
|
|
if (setenv(kSnapuserdFirstStageFdVar, value.c_str(), 1) < 0) {
|
|
|
|
PLOG(FATAL) << "setenv failed: " << kSnapuserdFirstStageFdVar << "=" << value;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
bool IsFirstStageSnapuserdRunning() {
|
|
|
|
return GetSnapuserdFirstStagePid().has_value();
|
|
|
|
}
|
|
|
|
|
2021-07-22 06:53:28 +02:00
|
|
|
std::vector<std::string> GetSnapuserdFirstStageInfo() {
|
|
|
|
const char* pid_str = getenv(kSnapuserdFirstStageInfoVar);
|
|
|
|
if (!pid_str) {
|
|
|
|
return {};
|
|
|
|
}
|
|
|
|
return android::base::Split(pid_str, ",");
|
|
|
|
}
|
|
|
|
|
init: Add an selinux transition for snapuserd.
With compressed VAB updates, it is not possible to mount /system without
first running snapuserd, which is the userspace component to the dm-user
kernel module. This poses a problem because as soon as selinux
enforcement is enabled, snapuserd (running in a kernel context) does not
have access to read and decompress the underlying system partition.
To account for this, we split SelinuxInitialize into multiple steps:
First, sepolicy is read into an in-memory string.
Second, the device-mapper tables for all snapshots are rebuilt. This
flushes any pending reads and creates new dm-user devices. The original
kernel-privileged snapuserd is then killed.
Third, sepolicy is loaded from the in-memory string.
Fourth, we re-launch snapuserd and connect it to the newly created
dm-user devices. As part of this step we restorecon device-mapper
devices and /dev/block/by-name/super, since the new snapuserd is in a
limited context.
Finally, we set enforcing mode.
This sequence ensures that snapuserd has appropriate privileges with a
minimal number of permissive audits.
Bug: 173476209
Test: full OTA with VABC applies and boots
Change-Id: Ie4e0f5166b01c31a6f337afc26fc58b96217604e
2020-12-08 09:21:20 +01:00
|
|
|
} // namespace init
|
|
|
|
} // namespace android
|