Re: [PATCH v2] x86: Fix build of UML with KASAN

2023-09-15 Thread Johannes Berg
On Fri, 2023-09-15 at 11:32 +0200, Ingo Molnar wrote: > > > ld: mm/kasan/shadow.o: in function `memset': > > shadow.c:(.text+0x40): multiple definition of `memset'; > > arch/x86/lib/memset_64.o:(.noinstr.text+0x0): first defined here > > ld: mm/kasan/shadow.o: in function `memmove': > > shado

Re: [PATCH v2] x86: Fix build of UML with KASAN

2023-09-15 Thread Ingo Molnar
* Vincent Whitchurch wrote: > Building UML with KASAN fails since commit 69d4c0d32186 ("entry, kasan, > x86: Disallow overriding mem*() functions") with the following errors: > > $ tools/testing/kunit/kunit.py run --kconfig_add CONFIG_KASAN=y > ... > ld: mm/kasan/shadow.o: in function `mems

[PATCH v2] x86: Fix build of UML with KASAN

2023-09-15 Thread Vincent Whitchurch
Building UML with KASAN fails since commit 69d4c0d32186 ("entry, kasan, x86: Disallow overriding mem*() functions") with the following errors: $ tools/testing/kunit/kunit.py run --kconfig_add CONFIG_KASAN=y ... ld: mm/kasan/shadow.o: in function `memset': shadow.c:(.text+0x40): multiple defini

printk_caller_id() crashing with UML/GCOV

2023-09-15 Thread Vimal Agrawal
I got following GCOV configs enabled CONFIG_GCOV_KERNEL=y CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y CONFIG_GCOV_PROFILE_ALL=y and was trying to run UML (kernel version 6.1.44) and ended up in a crash in printk_caller_id(). I tried to debug and it seems current_thread_info is returning NULL and that is