Lines Matching +full:disable +full:- +full:report +full:- +full:mask

1 .\"-
36 .Pa GENERIC-KMSAN
37 kernel configuration can be used to compile a KMSAN-enabled kernel using
42 .Bd -ragged -offset indent
73 runtime component and use hidden, byte-granular shadow state to determine
85 To report an error, the
94 In addition to compiler-detected uses of uninitialized memory,
114 The sanitizer in a KMSAN-configured kernel can be disabled by setting the loader
116 .Sy debug.kmsan.disable=1 .
139 mark device-written memory as initialized.
161 function and its sub-typed siblings validate the shadow state of the region(s)
164 a report.
183 A non-zero byte in the shadow map indicates that the corresponding byte of
196 Thus, operations on uninitialized state which raise a report may be far removed
201 report; when generating a report, the runtime uses state from the origin map
204 Unlike the shadow map, the origin map is not byte-granular, but consists of 4-byte
218 Files containing assembly code are left un-instrumented.
228 This is typically only necessary in machine-dependent code.
234 In addition to the shadow maps, the sanitizer requires some thread-local
244 To ensure that thread-local sanitizer state remains consistent, the
246 When machine-dependent interrupt and exception handlers begin execution,
258 .Bd -literal -offset indent
265 		/* A 2-byte hole is here. */
272 	 * This will raise a report since "sz" is uninitialized
274 	 * by the caller, a report would also be raised.
282 	 * This will raise a report since "buf" has not been
292 	 * This will raise a report since the pad bytes in "foo" have
299 	 * This line itself will not raise a report, but may trigger
300 	 * a report in the caller depending on how the return value is
340 mask bug in some kernel subsystems.
350 Some kernel memory allocators provide type-stable objects, and code which uses