Searched refs:redzone (Results 1 – 4 of 4) sorted by relevance
| /linux/tools/testing/selftests/powerpc/copyloops/ |
| H A D | validate.c | 22 unsigned long dst_off, unsigned long len, void *redzone, in do_one() argument
54 if (memcmp(dst, redzone, dstp - dst)) { in do_one()
60 if (memcmp(dstp+len, redzone, dst+BUFLEN-(dstp+len))) { in do_one()
69 char *src, *dst, *redzone, *fill; local
75 redzone = malloc(BUFLEN);
78 if (!src || !dst || !redzone || !fill) {
83 memset(redzone, POISON, BUFLEN);
97 redzone, fill);
|
| /linux/tools/mm/ |
| H A D | slabinfo.c | 92 int redzone; variable
688 redzone = 1; in debug_opt_scan()
707 if (redzone) in debug_opt_scan()
709 redzone = 1; in debug_opt_scan()
758 if (redzone && !s->red_zone) { in slab_debug()
764 if (!redzone && s->red_zone) { in slab_debug()
|
| /linux/Documentation/dev-tools/ |
| H A D | kfence.rst | 271 KFENCE also uses pattern-based redzones. For each object page, a redzone is set
272 up for all non-object memory. For typical alignments, the redzone is only
|
| H A D | kasan.rst | 260 partially accessible, freed, or be a part of a redzone. KASAN uses the following
|