[security] Make frro iteration thread-safe
Add a lock over all frro iterator methods to make sure the iterator isn't changed or removed from under the iteration call while it's running. + Also introduce an ID ensuring the caller is the same for all the acquire/next/release methods + a bit of moves where they were supposed to be from the start Bug: 245727875 Test: manual + presubmits Change-Id: Ie585b6d113ebddee491c9ee433f070bed71a57cc
Showing
- cmds/idmap2/idmap2d/Idmap2Service.cpp 26 additions, 11 deletionscmds/idmap2/idmap2d/Idmap2Service.cpp
- cmds/idmap2/idmap2d/Idmap2Service.h 8 additions, 3 deletionscmds/idmap2/idmap2d/Idmap2Service.h
- cmds/idmap2/idmap2d/aidl/services/android/os/IIdmap2.aidl 3 additions, 3 deletionscmds/idmap2/idmap2d/aidl/services/android/os/IIdmap2.aidl
- services/core/java/com/android/server/om/IdmapDaemon.java 5 additions, 4 deletionsservices/core/java/com/android/server/om/IdmapDaemon.java
Please register or sign in to comment