platform_system_core/debuggerd/tombstoned
Josh Gao 88846a2ccf Let system_server truncate tombstones.
There's no way to atomically unlink a specific file for which we have an fd from
a path, which means that we can't safely delete a tombstone without coordination
with tombstoned, which is risky. For example, if we use flock on the directory,
and system_server crashes while holding the lock, we risk deadlock.

We do the next best thing, and keep a file descriptor around for every
tombstone, and truncate it, which requires system_server to be able to
write to tombstones (which are owned by the system group).

Test: treehugger
Change-Id: I6ba7f1fe87ee1a4b57bdb3741e8ec9fbc80788c9
2021-02-01 17:48:58 -08:00
..
include/tombstoned Reland protobuf tombstones. 2021-01-26 17:55:17 -08:00
intercept_manager.cpp Reland protobuf tombstones. 2021-01-26 17:55:17 -08:00
intercept_manager.h tombstoned: allow intercepts for java traces. 2017-05-31 10:35:32 +01:00
tombstoned.cpp Let system_server truncate tombstones. 2021-02-01 17:48:58 -08:00
tombstoned.rc Start tombstoned early in post-fs-data. 2020-10-01 14:25:36 -07:00
tombstoned_client.cpp Reland protobuf tombstones. 2021-01-26 17:55:17 -08:00