Lines Matching +full:0 +full:x850

32   BUG: KMSAN: uninit-value in test_uninit_kmsan_check_memory+0x1be/0x380 [kmsan_test]
33    test_uninit_kmsan_check_memory+0x1be/0x380 mm/kmsan/kmsan_test.c:273
35    kunit_try_run_case+0x206/0x420 lib/kunit/test.c:374
36    kunit_generic_run_threadfn_adapter+0x6d/0xc0 lib/kunit/try-catch.c:28
37    kthread+0x721/0x850 kernel/kthread.c:327
38    ret_from_fork+0x1f/0x30 ??:?
41    do_uninit_local_array+0xfa/0x110 mm/kmsan/kmsan_test.c:260
42    test_uninit_kmsan_check_memory+0x1a2/0x380 mm/kmsan/kmsan_test.c:271
44    kunit_try_run_case+0x206/0x420 lib/kunit/test.c:374
45    kunit_generic_run_threadfn_adapter+0x6d/0xc0 lib/kunit/try-catch.c:28
46    kthread+0x721/0x850 kernel/kthread.c:327
47    ret_from_fork+0x1f/0x30 ??:?
50    do_uninit_local_array+0x4a/0x110 mm/kmsan/kmsan_test.c:256
51    test_uninit_kmsan_check_memory+0x1a2/0x380 mm/kmsan/kmsan_test.c:271
56   CPU: 0 PID: 6731 Comm: kunit_try_catch Tainted: G    B       E     5.16.0-rc3+ #104
57   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
138 setting its shadow bytes to ``0xff``) is called poisoning, marking it
139 initialized (setting the shadow bytes to ``0x00``) is called unpoisoning.
159   int a = 0xff;  // i.e. 0x000000ff
163 In this case the shadow of ``a`` is ``0``, shadow of ``b`` is ``0xffffffff``,
164 shadow of ``c`` is ``0xffffff00``. This means that the upper three bytes of
206     ret.s[0] = a;
212 0xffff0000, and the origin of the result would be the origin of ``b``.
213 ``ret.s[0]`` would have the same origin, but it will never be used, because