Handle an invalid new frame request

When HalCamera and VirtualCamera are synchronized based on the fences,
it is possible that VirtualCamera sends a new frame request after a
corresponding timeline/fence is destroyed.

This change therefore add a logic to check the validity of the timeline
associated with the requestor and, if it is not valid, returns an
invalid fence to notify that a frame request is not queued.

Fix: 169282240
Test: Run evs_halcamera_fuzzer and evs_virtualcamera_fuzzer
Change-Id: I783454bcdca05f8f4d6b2b8eff118956d7155362
Merged-In: I783454bcdca05f8f4d6b2b8eff118956d7155362
(cherry picked from commit 0b188826a3f9584f2cfed02d3a73d834c8312a60)
(cherry picked from commit a2163172e291093cba730f7113775442c8f8f244)
1 file changed
tree: bb7b7716637bc6140d15770e245461a78758623c
  1. car-bugreportd/
  2. car-default-input-service/
  3. car-internal-lib/
  4. car-lib/
  5. car-maps-placeholder/
  6. car-systemtest-lib/
  7. car-test-lib/
  8. car-usb-handler/
  9. car_product/
  10. computepipe/
  11. EncryptionRunner/
  12. evs/
  13. experimental/
  14. FrameworkPackageStubs/
  15. obd2-lib/
  16. packages/
  17. procfs-inspector/
  18. service/
  19. surround_view/
  20. tests/
  21. tools/
  22. user/
  23. vehicle-hal-support-lib/
  24. watchdog/
  25. .clang-format
  26. .gitignore
  27. Android.mk
  28. CleanSpec.mk
  29. CPPLINT.cfg
  30. OWNERS
  31. PREUPLOAD.cfg
  32. README.md

Native (C++) code format is required to be compatible with .clang-format file. Run

git clang-format --style=file --extension='h,cpp,cc' HEAD~

Note that clang-format is not desirable for Android java files. Therefore the command line above is limited to specific extensions.