diff options
| author | 2024-02-06 13:43:56 +0000 | |
|---|---|---|
| committer | 2024-02-15 14:16:20 +0000 | |
| commit | c2e43339544a06b8d77cb1cd2fc10fac3546fbaa (patch) | |
| tree | 4d038844fd620e07906218d9ec7fc2627d62f6b7 /api/coverage/tools | |
| parent | 3488035f49c18e3133f6fe1274faf793916df981 (diff) | |
Fix bug in eventTime comparison
The current logic when collecting Selinux events for logging is as
follows:
1. The first time the LogsService run, it collects events in the
[mLastWrite_N, mLastWrite_N+1] time bucket,
2. The next time, it collects events in the
[mLastWrite_N+1, mLastWrite_N+2] time bucket.
By this logic, events happening at time mLastWrite_N+1 are collected two
times. With this CL, a LogService run will collect events in the (mLastWrite_N+1, mLastWrite_N+2] bucket (startpoints excluded), avoiding the double collection.
Bug: 295861450
Test: atest SelinuxAuditLogsCollectorTest SelinuxAuditLogsBuilderTest
Change-Id: I3668e40789621db29b1dea73797fd56b6fd77bed
Diffstat (limited to 'api/coverage/tools')
0 files changed, 0 insertions, 0 deletions