tree ac39ab17801d626c06ea25b1863f7d211450750b
parent 800a2107428062666700208d490b51a1414d7f22
author Sahana Rao <sahanas@google.com> 1585587508 +0100
committer Sahana Rao <sahanas@google.com> 1587562991 +0100

Insert database row for apps bypassing scoped storage

Previously, for apps that bypassed scoped storage restrictions, scanFile
was used to insert a new database row for files created through file
path. ScanFile was called on FUSE RELEASE op which is a non-blocking
call. This can introduce some race conditions(Refer b/149989434). Now,
instead of calling scanFile, we insert a new database row on FUSE create.

Inserting a database row for files created through filePath but not
deleting the database row on delete might break some app functionality.

Keeping the insert code commented until we start deleting the database
row on FUSE unlink.

Test: atest FuseDaemonHostTest
Bug: 149989434
Change-Id: I9e50bb3aa69c5caf8975153403783c2483982068