Searched refs:poison (Results 1 – 16 of 16) sorted by relevance
| /Linux-v5.4/tools/testing/selftests/powerpc/tm/ |
| D | tm-poison.c | 31 uint64_t poison = 0xdeadbeefc0dec0fe; in tm_poison_test() local
54 : : [poison] "r" (poison) : ); in tm_poison_test()
|
| D | .gitignore | 20 tm-poison
|
| D | Makefile | 8 tm-signal-context-force-tm tm-poison
|
| /Linux-v5.4/mm/ |
| D | Kconfig.debug | 29 fill the pages with poison patterns after free_pages() and verify
69 Fill the pages with poison patterns after free_pages() and verify
75 Note that "poison" here is not the same thing as the "HWPoison"
82 bool "Only poison, don't sanity check"
85 poison on free. This reduces some of the overhead of the
95 Instead of using the existing poison value, fill the pages with
|
| D | page_alloc.c | 7485 unsigned long free_reserved_area(void *start, void *end, int poison, const char *s) in free_reserved_area() argument
7504 if ((unsigned int)poison <= 0xFF) in free_reserved_area()
7505 memset(direct_map_addr, poison, PAGE_SIZE); in free_reserved_area()
|
| D | slub.c | 5221 SLAB_ATTR(poison);
|
| /Linux-v5.4/tools/vm/ |
| D | slabinfo.c | 35 int order, poison, reclaim_account, red_zone; member
93 int poison; variable
555 page_size << s->order, s->partial, onoff(s->poison), in report()
611 if (s->poison) in slabcache()
660 poison = 1; in debug_opt_scan()
674 if (poison) in debug_opt_scan()
676 poison = 1; in debug_opt_scan()
743 if (poison && !s->poison) { in slab_debug()
749 if (!poison && s->poison) { in slab_debug()
1230 slab->poison = get_obj("poison"); in read_slab_dir()
|
| /Linux-v5.4/Documentation/vm/ |
| D | hwpoison.rst | 44 a new page poison bit and various checks in the VM to handle poisoned
151 page-types -p `pidof usemem` --hwpoison # poison its pages
154 When specified, only poison pages if ((page_flags & mask) ==
|
| D | slub.rst | 68 example, here's how you can poison the dentry cache as well as all kmalloc
234 typically contain poison values. Any non-poison value shows a
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-bus-nfit | 183 the address (cache line) where the MCE happened to the poison
190 insert the address of the memory error into the poison and
|
| D | sysfs-kernel-slab | 375 What: /sys/kernel/slab/cache/poison
381 The poison file specifies whether objects should be poisoned
|
| /Linux-v5.4/Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 118 One other variant 2 attack vector is for the attacker to poison the
121 imbalanced subroutine call instructions might "poison" entries in the
191 A spectre variant 2 attacker can :ref:`poison <poison_btb>` the branch
272 For Spectre variant 2 attacks, rogue guests can :ref:`poison
|
| /Linux-v5.4/security/ |
| D | Kconfig.hardening | 120 the stack initialized to the poison value, which both reduces
|
| /Linux-v5.4/include/linux/ |
| D | mm.h | 2074 int poison, const char *s);
2115 static inline unsigned long free_initmem_default(int poison) in free_initmem_default() argument
2120 poison, "unused kernel"); in free_initmem_default()
|
| /Linux-v5.4/Documentation/security/ |
| D | self-protection.rst | 305 When releasing memory, it is best to poison the contents, to avoid reuse
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | kernel-parameters.txt | 4365 may poison objects when not in use. Also tracks the
|
