| commit | 2cb13ead22f7702acdda4f159ef73fb077649894 | [log] [tgz] |
|---|---|---|
| author | Primiano Tucci <primiano@google.com> | Fri Jan 14 20:32:15 2022 +0000 |
| committer | Primiano Tucci <primiano@google.com> | Fri Jan 14 23:28:39 2022 +0000 |
| tree | 32563d50ca67f6cc4ccf02be07bf291ad45e555c | |
| parent | 06d1177ec0ba35db72e7a14108c6f43d81473492 [diff] [blame] |
Add traced_probes and traced_perf to readtracefd group After the kernel changes [1,2,3] and the matching userspace CLs [4], any process that needs to access ftrace needs to be part of the readtracefs capability group introduced by aosp/1912638. [1] https://lore.kernel.org/all/20211115165350.976783364@linuxfoundation.org/ [2] https://lore.kernel.org/all/20211213092927.298812141@linuxfoundation.org/ [3] https://lore.kernel.org/all/20211213092927.108231338@linuxfoundation.org/ [4] https://android-review.googlesource.com/q/topic:tracefs-access Test: manual (m, test various perfetto configs) Bug: 209513178 Bug: 214591300 Bug: 212364925 Change-Id: I6ce3d60983601087f2bb5801951fb5e1a86c1220
diff --git a/traced_perf.rc b/traced_perf.rc index 1835466..7b0ec6a 100644 --- a/traced_perf.rc +++ b/traced_perf.rc
@@ -25,7 +25,7 @@ disabled socket traced_perf stream 0666 root root user nobody - group nobody readproc + group nobody readproc readtracefs capabilities KILL DAC_READ_SEARCH task_profiles ProcessCapacityHigh