Lines Matching refs:close

8 …file descriptor ownership, which tend to manifest as *use-after-close* and *double-close*. These e…
14     close(fd);
15     close(fd);
31 close(123) = 0
33 close(123) = 0
43 …nctions to associate a file descriptor with an owner; if someone tries to close a file descriptor …
45 …cases where it's hard to derive an identifier for the "owner" that should close a file descriptor,…
91   close(fd);
98   close(fd);
103   close(fd);
105   close(fd);
124                                                                   close(3);
126                                                                   close(3);
128                                   close(3);
152 -  close(fd);
158 … we've guarded the file descriptor with fdsan, we should be able to find where the double close is:
163 Abort message: 'attempted to close file descriptor 3, expected to be unowned, actually owned by uni…
177     #02 pc 00000000000092a0  /system/lib64/libc.so (close+16)
186 …hat the culprit closed `bystander`'s file descriptor between its open and close, which resulted in…
197 -  close(fd);
204 Abort message: 'attempted to close file descriptor 3, expected to be unowned, actually owned by uni…
218     #02 pc 00000000000092a0  /system/lib64/libc.so (close+16)
231 …imitives. `android_fdsan_exchange_owner_tag` modifies a file descriptor's close tag, and `android_…
321             close(fd_, tag());
343     // if available, and fall back to no-ops or regular close on pre-Q devices.
350     static int close(int fd, uint64_t tag) {
354             return ::close(fd);
364 …leDescriptor` via Intent, and then passing it into JNI code that ends up calling close on it. <br/>
371 2. [<b><i>50%</i></b> of Facebook's iOS crashes caused by a file descriptor double close leading to…