2009-03-04 03:32:55 +00:00
|
|
|
/*
|
|
|
|
* Copyright (C) 2007 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.
|
|
|
|
*/
|
|
|
|
|
2019-04-18 21:18:36 +00:00
|
|
|
#pragma once
|
2009-03-04 03:32:55 +00:00
|
|
|
|
2015-10-01 23:03:47 +00:00
|
|
|
#include <sys/socket.h>
|
2017-04-06 23:30:22 +00:00
|
|
|
|
init: Handle properties in the background of calling fs_mgr
It's been a long standing problem that init calls fs_mgr functions
synchronously and therefore stops handling properties, which causes
deadlocks if either fs_mgr, or vdc, or vold attempt to set
properties.
Previous work, b/21904461, shows that there is a large performance
penalty for adding any amount of locking to properties, so moving
property service into its own thread generically is not a viable
option. However, we can be sure that init is not setting properties
while the fs_mgr functions are running, so we can poll the property
socket in a thread while we call these functions.
The other alternative would have been to separate the fs_mgr functions
into smaller pieces and revisit the main init loop between each
piece. Unfortunately, this would be difficult, since
fs_mgr_mount_all() calls out to different processes via logwrapper,
which synchronously polls on a logging FD from the child, among other
complexities that would make this strategy much more difficult than it
would be worth.
Bug: 21904461
Test: device boots, including when setting property in
fs_mgr_mount_all()
Change-Id: Ib0b7123024035884f9d90f9b489c1e2f5a2e1707
2019-06-17 22:47:09 +00:00
|
|
|
#include <functional>
|
2015-07-24 17:11:05 +00:00
|
|
|
#include <string>
|
2011-09-06 17:12:21 +00:00
|
|
|
|
2015-10-24 23:20:18 +00:00
|
|
|
#include "epoll.h"
|
init: Handle properties in the background of calling fs_mgr
It's been a long standing problem that init calls fs_mgr functions
synchronously and therefore stops handling properties, which causes
deadlocks if either fs_mgr, or vdc, or vold attempt to set
properties.
Previous work, b/21904461, shows that there is a large performance
penalty for adding any amount of locking to properties, so moving
property service into its own thread generically is not a viable
option. However, we can be sure that init is not setting properties
while the fs_mgr functions are running, so we can poll the property
socket in a thread while we call these functions.
The other alternative would have been to separate the fs_mgr functions
into smaller pieces and revisit the main init loop between each
piece. Unfortunately, this would be difficult, since
fs_mgr_mount_all() calls out to different processes via logwrapper,
which synchronously polls on a logging FD from the child, among other
complexities that would make this strategy much more difficult than it
would be worth.
Bug: 21904461
Test: device boots, including when setting property in
fs_mgr_mount_all()
Change-Id: Ib0b7123024035884f9d90f9b489c1e2f5a2e1707
2019-06-17 22:47:09 +00:00
|
|
|
#include "result.h"
|
2015-10-24 23:20:18 +00:00
|
|
|
|
2017-06-22 19:53:17 +00:00
|
|
|
namespace android {
|
|
|
|
namespace init {
|
|
|
|
|
2018-10-22 21:50:52 +00:00
|
|
|
bool CanReadProperty(const std::string& source_context, const std::string& name);
|
|
|
|
|
2018-01-19 00:14:25 +00:00
|
|
|
extern uint32_t (*property_set)(const std::string& name, const std::string& value);
|
|
|
|
|
|
|
|
uint32_t HandlePropertySet(const std::string& name, const std::string& value,
|
2018-03-01 19:00:57 +00:00
|
|
|
const std::string& source_context, const ucred& cr, std::string* error);
|
2018-01-19 00:14:25 +00:00
|
|
|
|
2019-04-18 21:18:36 +00:00
|
|
|
void property_init();
|
|
|
|
void property_load_boot_defaults(bool load_debug_prop);
|
|
|
|
void load_persist_props();
|
2015-10-24 23:20:18 +00:00
|
|
|
void StartPropertyService(Epoll* epoll);
|
2009-03-04 03:32:55 +00:00
|
|
|
|
init: Handle properties in the background of calling fs_mgr
It's been a long standing problem that init calls fs_mgr functions
synchronously and therefore stops handling properties, which causes
deadlocks if either fs_mgr, or vdc, or vold attempt to set
properties.
Previous work, b/21904461, shows that there is a large performance
penalty for adding any amount of locking to properties, so moving
property service into its own thread generically is not a viable
option. However, we can be sure that init is not setting properties
while the fs_mgr functions are running, so we can poll the property
socket in a thread while we call these functions.
The other alternative would have been to separate the fs_mgr functions
into smaller pieces and revisit the main init loop between each
piece. Unfortunately, this would be difficult, since
fs_mgr_mount_all() calls out to different processes via logwrapper,
which synchronously polls on a logging FD from the child, among other
complexities that would make this strategy much more difficult than it
would be worth.
Bug: 21904461
Test: device boots, including when setting property in
fs_mgr_mount_all()
Change-Id: Ib0b7123024035884f9d90f9b489c1e2f5a2e1707
2019-06-17 22:47:09 +00:00
|
|
|
template <typename F, typename... Args>
|
|
|
|
Result<int> CallFunctionAndHandleProperties(F&& f, Args&&... args) {
|
|
|
|
Result<int> CallFunctionAndHandlePropertiesImpl(const std::function<int()>& f);
|
|
|
|
|
|
|
|
auto func = [&] { return f(args...); };
|
|
|
|
return CallFunctionAndHandlePropertiesImpl(func);
|
|
|
|
}
|
|
|
|
|
2017-06-22 19:53:17 +00:00
|
|
|
} // namespace init
|
|
|
|
} // namespace android
|