Home
last modified time | relevance | path

Searched refs:poisoned (Results 1 – 18 of 18) sorted by relevance

/OK3568_Linux_fs/buildroot/package/dillo/
H A D0001-usr-local-include.patch1 Do not add (possibly poisoned) /usr/local/include and /usr/local/lib
4 With BR2_COMPILER_PARANOID_UNSAFE_PATH enabled, poisoned paths result
/OK3568_Linux_fs/kernel/Documentation/ABI/testing/
H A Dsysfs-memory-page-offline17 The page must be still accessible, not poisoned. The
35 to access this page assuming it's poisoned by the
H A Dsysfs-kernel-slab383 The poison file specifies whether objects should be poisoned
/OK3568_Linux_fs/kernel/drivers/usb/core/
H A Durb.c135 if (unlikely(anchor->poisoned)) in usb_anchor_urb()
857 anchor->poisoned = 1; in usb_poison_anchored_urbs()
893 anchor->poisoned = 0; in usb_unpoison_anchored_urbs()
/OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/gcc/gcc/
H A D0002-gcc-poison-system-directories.patch119 +AC_MSG_NOTICE([poisoned directories $enable_poison_system_directories])
121 + AC_MSG_NOTICE([poisoned directories enabled])
126 + AC_MSG_NOTICE([poisoned directories are fatal])
/OK3568_Linux_fs/kernel/Documentation/admin-guide/hw-vuln/
H A Dspectre.rst206 After entering the kernel, the kernel could use the poisoned branch
215 The kernel can protect itself against consuming poisoned branch
266 a deeper call stack. Any poisoned entries in the return stack buffer
290 for indirect branches to bypass the poisoned branch target buffer,
312 stack buffer. Such poisoned entries could be used to influence
506 This protects them from consuming poisoned entries in the branch
539 poisoned entries in branch target buffer left by rogue guests. It also
541 stack buffer underflow so poisoned branch target buffer could be used,
542 or attacker guests leaving poisoned entries in the return stack buffer.
/OK3568_Linux_fs/kernel/Documentation/vm/
H A Dhwpoison.rst11 (``MCA recovery``). This requires the OS to declare a page "poisoned",
44 a new page poison bit and various checks in the VM to handle poisoned
/OK3568_Linux_fs/yocto/poky/documentation/migration-guides/
H A Dmigration-1.8.rst107 ``gcc's`` default sysroot and include directories are now "poisoned". In
/OK3568_Linux_fs/kernel/include/linux/
H A Dusb.h1393 unsigned int poisoned:1; member
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/info/
H A Dcppinternals.info244 Some identifiers, such as '__VA_ARGS__' and poisoned identifiers, may
250 issue a diagnostic for re-poisoning a poisoned identifier, or for using
H A Dcpp.info2287 '#if', and they cannot be defined as macros or poisoned. In C, you can
3400 If a poisoned identifier appears as part of the expansion of a
3401 macro which was defined before the identifier was poisoned, it will
H A Dgccint.info45508 | |: sval: sv1: {poisoned: uninit}
45524 |: sval: sv2: {poisoned: uninit}
45528 sv1: {poisoned: uninit}
45529 sv2: {poisoned: uninit}
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/info/
H A Dcppinternals.info244 Some identifiers, such as '__VA_ARGS__' and poisoned identifiers, may
250 issue a diagnostic for re-poisoning a poisoned identifier, or for using
H A Dcpp.info2287 '#if', and they cannot be defined as macros or poisoned. In C, you can
3400 If a poisoned identifier appears as part of the expansion of a
3401 macro which was defined before the identifier was poisoned, it will
H A Dgccint.info45508 | |: sval: sv1: {poisoned: uninit}
45524 |: sval: sv2: {poisoned: uninit}
45528 sv1: {poisoned: uninit}
45529 sv2: {poisoned: uninit}
/OK3568_Linux_fs/kernel/Documentation/driver-api/
H A Dlibata.rst519 2. ``ap->active_tag`` and ``qc->tag`` are poisoned.
/OK3568_Linux_fs/kernel/kernel/bpf/
H A Dverifier.c225 bool poisoned = bpf_map_key_poisoned(aux); in bpf_map_key_store() local
228 (poisoned ? BPF_MAP_KEY_POISON : 0ULL); in bpf_map_key_store()
/OK3568_Linux_fs/external/xserver/
H A DChangeLog31679 client information gets const poisoned. Worked around by adding a