Searched refs:randomized (Results 1 – 10 of 10) sorted by relevance
31 of the kernel to be randomized at build-time. When selected,32 this option will cause TEXT_OFFSET to be randomized upon any
1217 When this option is not set, the module region will be randomized over
74 physical memory, vmalloc/ioremap space and virtual memory map are randomized.
109 marked with __randomize_layout, will be randomized at compile-time.
5 guided fuzzing (randomized testing). Coverage data of a running kernel is
1012 bool randomized = nand->options & NAND_NEED_SCRAMBLING; in sunxi_nfc_hw_ecc_read_chunks_dma() local1062 ret = sunxi_nfc_hw_ecc_correct(mtd, randomized ? data : NULL, in sunxi_nfc_hw_ecc_read_chunks_dma()1101 if (randomized) in sunxi_nfc_hw_ecc_read_chunks_dma()
835 1 - Make the addresses of mmap base, stack and VDSO page randomized.838 location of code start is randomized. This is the default if the847 start of the brk area is randomized. There are however no known
2118 randomized separately. The physical address will be anywhere2120 virtual address will be randomized from 16MB up to 1GB (9 bits2125 randomized together. They will be randomized from 16MB up to2297 kernel space. Since this location is not randomized with ASLR,
569 An architecture supports choosing randomized locations for
755 for coverage-guided fuzzing (randomized testing).
