https://bugzilla.kernel.org/show_bug.cgi?id=205099
--- Comment #34 from Erhard F. (erhar...@mailbox.org) --- Created attachment 299711 --> https://bugzilla.kernel.org/attachment.cgi?id=299711&action=edit dmesg (5.15.5, OUTLINE KASAN, PowerMac G4 DP) Finally my G4 DP got its' fixed & overhauled PSU so I am able to continue here. Tested kernel 5.15.5 and the original KASAN hit at raid6_pq did not show up. Instead I am getting this now: [...] Running code patching self-tests ... vmap allocation for size 33562624 failed: use vmalloc=<size> to increase size swapper/0: vmalloc error: size 33558528, vm_struct allocation failed, mode:0xcc0(GFP_KERNEL), nodemask=(null) CPU: 0 PID: 1 Comm: swapper/0 Tainted: G W 5.15.5-gentoo-PowerMacG4 #5 Call Trace: [f1033bb0] [c0d933c0] dump_stack_lvl+0x80/0xb0 (unreliable) [f1033bd0] [c0516128] warn_alloc+0x11c/0x2b4 [f1033cb0] [c0508c40] __vmalloc_node_range+0xd8/0x64c [f1033d70] [c0508a58] __vmalloc_node+0xec/0xf4 [f1033db0] [c1c0ecb0] test_code_patching+0x72c/0xd50 [f1033df0] [c0008908] do_one_initcall+0x284/0x574 [f1033ec0] [c1c03f78] kernel_init_freeable+0x510/0x51c [f1033f10] [c000934c] kernel_init+0x24/0x140 [f1033f30] [c0033148] ret_from_kernel_thread+0x14/0x1c Mem-Info: active_anon:0 inactive_anon:0 isolated_anon:0 active_file:0 inactive_file:0 isolated_file:0 unevictable:0 dirty:0 writeback:0 slab_reclaimable:1306 slab_unreclaimable:4214 mapped:0 shmem:0 pagetables:0 bounce:0 kernel_misc_reclaimable:0 free:474459 free_pcp:592 free_cma:0 Node 0 active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:0kB dirty:0kB writeback:0kB shmem:0kB writeback_tmp:0kB kernel_stack:840kB pagetables:0kB all_unreclaimable? no DMA free:588612kB min:3144kB low:3928kB high:4712kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:786432kB managed:618264kB mlocked:0kB bounce:0kB free_pcp:1964kB local_pcp:1568kB free_cma:0kB lowmem_reserve[]: 0 0 1280 1280 HighMem free:1309224kB min:512kB low:2176kB high:3840kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:1310720kB managed:1310720kB mlocked:0kB bounce:0kB free_pcp:404kB local_pcp:116kB free_cma:0kB lowmem_reserve[]: 0 0 0 0 DMA: 5*4kB (ME) 2*8kB (UM) 4*16kB (M) 5*32kB (ME) 1*64kB (M) 4*128kB (UME) 4*256kB (ME) 4*512kB (UM) 3*1024kB (M) 4*2048kB (ME) 140*4096kB (M) = 588612kB HighMem: 0*4kB 1*8kB (U) 0*16kB 1*32kB (U) 0*64kB 2*128kB (U) 1*256kB (U) 0*512kB 0*1024kB 1*2048kB (U) 319*4096kB (M) = 1309224kB 0 total pagecache pages 0 pages in swap cache Swap cache stats: add 0, delete 0, find 0/0 Free swap = 0kB Total swap = 0kB 524288 pages RAM 327680 pages HighMem/MovableOnly 42042 pages reserved code-patching: test failed at line 598 [...] This makes me wonder whether KASAN is working correctly when not enough vmap size is available. I did set it to vmalloc=64M via Kernel command line but this does not seem to be reckognized. Same situation with INLINE KASAN. In both cases with VMAP_STACK and CONFIG_THREAD_SHIFT=14. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
