Lines Matching refs:to

5 fdsan is a file descriptor sanitizer added to Android in API level 29.
10 *What problem is fdsan trying to solve? Why should I care?*
12 …to manifest as *use-after-close* and *double-close*. These errors are direct analogues of the memo…
42 … (e.g. suppose thread two was saving user data to disk when a third thread came in and opened a so…
47 …to detect and/or prevent file descriptor mismanagement by enforcing file descriptor ownership. Lik…
49 …to set a 64-bit closure tag on a file descriptor. The tag consists of an 8-bit type byte that iden…
59 …- Upon detecting an error, emit a warning to logcat, generate a tombstone, and then continue execu…
67 The likelihood of fdsan catching a file descriptor error is proportional to the percentage of file …
69 ### Using fdsan to fix a bug
72 Let's look at a simple contrived example that uses sleeps to force a particular interleaving of thr…
93     err(1, "good failed to write?!");
138     fdsan_test: good failed to write?!: Bad file descriptor
140 …pfully closing it for us. Let's use `android::base::unique_fd` in `victim` to guard the file descr…
154      err(1, "good failed to write?!");
162 Now that we've guarded the file descriptor with fdsan, we should be able to find where the double c…
167 Abort message: 'attempted to close file descriptor 3, expected to be unowned, actually owned by uni…
208 Abort message: 'attempted to close file descriptor 3, expected to be unowned, actually owned by uni…
231 …to be as detectable or reproducible as our toy example, which is a good reason to try to maximize …
340     // The obvious choice of tag to use is the address of the object.
347     // if available, and fall back to no-ops or regular close on pre-Q devices.
375 2. [<b><i>50%</i></b> of Facebook's iOS crashes caused by a file descriptor double close leading to…