Lines Matching full:based

16 2. Software Tag-Based KASAN
17 3. Hardware Tag-Based KASAN
23 Software Tag-Based KASAN or SW_TAGS KASAN, enabled with CONFIG_KASAN_SW_TAGS,
28 Hardware Tag-Based KASAN or HW_TAGS KASAN, enabled with CONFIG_KASAN_HW_TAGS,
37 The Generic and the Software Tag-Based modes are commonly referred to as the
38 software modes. The Software Tag-Based and the Hardware Tag-Based modes are
39 referred to as the tag-based modes.
48 and loongarch, and the tag-based KASAN modes are supported only on arm64.
55 support for that. The Hardware Tag-Based mode relies on hardware to perform
62 Software Tag-Based KASAN requires GCC 11+
65 Hardware Tag-Based KASAN requires GCC 10+ or Clang 12+.
73 Software Tag-Based KASAN supports slab, page_alloc, vmalloc, and stack memory.
75 Hardware Tag-Based KASAN supports slab, page_alloc, and non-executable vmalloc
79 Hardware Tag-Based KASAN only supports SLUB.
89 ``CONFIG_KASAN_SW_TAGS`` (to enable Software Tag-Based KASAN), and
90 ``CONFIG_KASAN_HW_TAGS`` (to enable Hardware Tag-Based KASAN).
117   Hardware Tag-Based KASAN, ``kasan.fault=panic_on_write`` always panics on
120 Software and Hardware Tag-Based KASAN modes (see the section about various
128 Hardware Tag-Based KASAN mode is intended for use in production as a security
158   Note that enabling this parameter makes Hardware Tag-Based KASAN skip checks
271 For tag-based KASAN modes, this last report section shows the memory tags around
275 are best-effort: KASAN prints the most probable bug type based on the limited
342 Software Tag-Based KASAN
345 Software Tag-Based KASAN uses a software memory tagging approach to checking
348 Software Tag-Based KASAN uses the Top Byte Ignore (TBI) feature of arm64 CPUs
353 On each memory allocation, Software Tag-Based KASAN generates a random tag, tags
357 Software Tag-Based KASAN uses compile-time instrumentation to insert checks
360 this memory. In case of a tag mismatch, Software Tag-Based KASAN prints a bug
363 Software Tag-Based KASAN also has two instrumentation modes (outline, which
370 Software Tag-Based KASAN uses 0xFF as a match-all pointer tag (accesses through
374 Hardware Tag-Based KASAN
377 Hardware Tag-Based KASAN is similar to the software mode in concept but uses
381 Hardware Tag-Based KASAN is currently only implemented for arm64 architecture
382 and based on both arm64 Memory Tagging Extension (MTE) introduced in ARMv8.5
391 Hardware Tag-Based KASAN uses 0xFF as a match-all pointer tag (accesses through
395 If the hardware does not support MTE (pre ARMv8.5), Hardware Tag-Based KASAN
402 Hardware Tag-Based KASAN only reports the first found bug. After that, MTE tag
501 Tag-Based KASAN, which does not use compiler instrumentation.
508 For tag-based KASAN modes, to disable access checking, use