88846a2ccf
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 |
||
---|---|---|
.. | ||
include/tombstoned | ||
intercept_manager.cpp | ||
intercept_manager.h | ||
tombstoned.cpp | ||
tombstoned.rc | ||
tombstoned_client.cpp |