Searched refs:arbitrary (Results 1 – 19 of 19) sorted by relevance
7 # Write to arbitrary pipes given to us.
19 # To resolve arbitrary sysfs paths from /sys/class/wakeup/* symlinks.
10 # should never be read or written. To avoid giving arbitrary processes access to /dev/boringssl
235 # Do not permit access from apps which host arbitrary code to the protected services
868 # Vendor apps are permited to use only stable public services. If they were to use arbitrary1871 # Protect most domains from executing arbitrary content from /data.
24 // Payload is arbitrary.
279 auto arbitrary = data[ARBITRARY]; in TEST() local280 ASSERT_EQ(0, arbitrary.i0); in TEST()281 ASSERT_EQ(2, arbitrary.v1[1]); in TEST()282 ASSERT_EQ(4, arbitrary.p2.first); in TEST()
50 Additionally, OEMs can specify `BOARD_SEPOLICY_M4DEFS` to pass arbitrary `m4`70 as well as mapping a public base16 signing key with an arbitrary seinfo81 Is a helper script for mapping arbitrary tags in the signature stanzas of
19 use libfuzzer_sys::arbitrary::Arbitrary;
42 <td>Field that the benchmark can fill with an arbitrary string.
32 # sysfs attributes, not on arbitrary paths.
5 spaces that can hold arbitrary data blobs of limited size. Access restrictions
30 use libfuzzer_sys::{arbitrary::Arbitrary, fuzz_target};
28 # Allow loading of arbitrary C extensions. Extensions are imported into the29 # active Python interpreter and may run arbitrary code.34 # run arbitrary code
41 # Allow loading of arbitrary C extensions. Extensions are imported into the42 # active Python interpreter and may run arbitrary code.47 # run arbitrary code
27 # Allow loading of arbitrary C extensions. Extensions are imported into the28 # active Python interpreter and may run arbitrary code.
32 /// Vector containing arbitrary application-specific message data
170 *events* with arbitrary binary payload. Event IDs starting in the range
40 b. TEXT -> the remaining 252 bytes are arbitrary. They should