* boot failure of linux-next due to 1248fb6a8201 ("x86/mm: Randomize per-cpu entry area")
@ 2022-10-28 13:29 Sudip Mukherjee (Codethink)
2022-10-28 14:33 ` Dave Hansen
2022-10-28 16:41 ` Kees Cook
0 siblings, 2 replies; 5+ messages in thread
From: Sudip Mukherjee (Codethink) @ 2022-10-28 13:29 UTC (permalink / raw)
To: Peter Zijlstra, Dave Hansen, Kees Cook
Cc: Thomas Gleixner, Ingo Molnar, Borislav Petkov, Dave Hansen, x86,
H. Peter Anvin, Andy Lutomirski, linux-kernel, linux-next
Hi All,
Our qemu boots were failing since next-20221024, and a git bisect of
next-20221028 showed the bad commit as 1248fb6a8201 ("x86/mm: Randomize per-cpu entry area")
After reverting the commit I could boot qemu again with next-20221028.
This is my config:
make defconfig
make kvm_guest.config
scripts/config -e KCOV -e KCOV_INSTRUMENT_ALL -e KCOV_ENABLE_COMPARISONS -e DEBUG_FS -e DEBUG_KMEMLEAK -e DEBUG_INFO -e KALLSYMS -e KALLSYMS_ALL -e NAMESPACES -e UTS_NS -e IPC_NS -e PID_NS -e NET_NS -e CGROUP_PIDS -e MEMCG -e USER_NS -e CONFIGFS_FS -e SECURITYFS -e KASAN -e KASAN_INLINE -e FAULT_INJECTION -e FAULT_INJECTION_DEBUG_FS -e FAULT_INJECTION_USERCOPY -e FAILSLAB -e FAIL_PAGE_ALLOC -e FAIL_MAKE_REQUEST -e FAIL_IO_TIMEOUT -e FAIL_FUTEX -e LOCKDEP -e PROVE_LOCKING -e DEBUG_ATOMIC_SLEEP -e PROVE_RCU -e DEBUG_VM -e REFCOUNT_FULL -e FORTIFY_SOURCE -e HARDENED_USERCOPY -e LOCKUP_DETECTOR -e SOFTLOCKUP_DETECTOR -e HARDLOCKUP_DETECTOR -e BOOTPARAM_HARDLOCKUP_PANIC -e DETECT_HUNG_TASK -e WQ_WATCHDOG -e USB_GADGET -e USB_RAW_GADGET -e TUN -e KCSAN -d RANDOMIZE_BASE -e MAC80211_HWSIM -e IEEE802154 -e MAC802154 -e IEEE802154_DRIVERS -e IEEE802154_HWSIM -e BT -e BT_HCIVHCI
echo "CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=140" >> .config
echo "CONFIG_RCU_CPU_STALL_TIMEOUT=100" >> .config
I will be happy to test any patch or provide any extra log if needed.
Though I am not sure how I will collect extra logs (if needed) as there
was no output from qemu.
--
Regards
Sudip
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: boot failure of linux-next due to 1248fb6a8201 ("x86/mm: Randomize per-cpu entry area") 2022-10-28 13:29 boot failure of linux-next due to 1248fb6a8201 ("x86/mm: Randomize per-cpu entry area") Sudip Mukherjee (Codethink) @ 2022-10-28 14:33 ` Dave Hansen 2022-10-28 16:06 ` Sudip Mukherjee 2022-10-28 16:41 ` Kees Cook 1 sibling, 1 reply; 5+ messages in thread From: Dave Hansen @ 2022-10-28 14:33 UTC (permalink / raw) To: Sudip Mukherjee (Codethink), Peter Zijlstra, Dave Hansen, Kees Cook Cc: Thomas Gleixner, Ingo Molnar, Borislav Petkov, x86, H. Peter Anvin, Andy Lutomirski, linux-kernel, linux-next On 10/28/22 06:29, Sudip Mukherjee (Codethink) wrote: > I will be happy to test any patch or provide any extra log if needed. > Though I am not sure how I will collect extra logs (if needed) as there > was no output from qemu. Could you share your qemu config? The command-line would be fine. Does it have a serial console set up? ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: boot failure of linux-next due to 1248fb6a8201 ("x86/mm: Randomize per-cpu entry area") 2022-10-28 14:33 ` Dave Hansen @ 2022-10-28 16:06 ` Sudip Mukherjee 0 siblings, 0 replies; 5+ messages in thread From: Sudip Mukherjee @ 2022-10-28 16:06 UTC (permalink / raw) To: Dave Hansen Cc: Peter Zijlstra, Dave Hansen, Kees Cook, Thomas Gleixner, Ingo Molnar, Borislav Petkov, x86, H. Peter Anvin, Andy Lutomirski, linux-kernel, linux-next On Fri, Oct 28, 2022 at 3:33 PM Dave Hansen <dave.hansen@intel.com> wrote: > > On 10/28/22 06:29, Sudip Mukherjee (Codethink) wrote: > > I will be happy to test any patch or provide any extra log if needed. > > Though I am not sure how I will collect extra logs (if needed) as there > > was no output from qemu. > > Could you share your qemu config? The command-line would be fine. Does > it have a serial console set up? qemu-system-x86_64 -m 2048 -smp 2 -chardev socket,id=SOCKSYZ,server,nowait,host=localhost,port=46514 -mon chardev=SOCKSYZ,mode=control -display none -serial stdio -no-reboot -name VM-test -device virtio-rng-pci -enable-kvm -cpu host,migratable=off -device e1000,netdev=net0 -netdev user,id=net0,restrict=on,hostfwd=tcp:127.0.0.1:28993-:22 -hda bullseye.img -snapshot -kernel bzImage -append "root=/dev/sda console=ttyS0 net.ifnames=0 biosdevname=0" serial is via stdio, and in normal boots I get the bootlog in the terminal, but in this case there was nothing. -- Regards Sudip ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: boot failure of linux-next due to 1248fb6a8201 ("x86/mm: Randomize per-cpu entry area") 2022-10-28 13:29 boot failure of linux-next due to 1248fb6a8201 ("x86/mm: Randomize per-cpu entry area") Sudip Mukherjee (Codethink) 2022-10-28 14:33 ` Dave Hansen @ 2022-10-28 16:41 ` Kees Cook 2022-10-28 20:04 ` Sudip Mukherjee 1 sibling, 1 reply; 5+ messages in thread From: Kees Cook @ 2022-10-28 16:41 UTC (permalink / raw) To: Sudip Mukherjee (Codethink) Cc: Peter Zijlstra, Dave Hansen, Thomas Gleixner, Ingo Molnar, Borislav Petkov, x86, H. Peter Anvin, Andy Lutomirski, linux-kernel, linux-next On Fri, Oct 28, 2022 at 02:29:14PM +0100, Sudip Mukherjee (Codethink) wrote: > Hi All, > > Our qemu boots were failing since next-20221024, and a git bisect of > next-20221028 showed the bad commit as 1248fb6a8201 ("x86/mm: Randomize per-cpu entry area") > > After reverting the commit I could boot qemu again with next-20221028. > > This is my config: > > make defconfig > make kvm_guest.config > scripts/config -e KCOV -e KCOV_INSTRUMENT_ALL -e KCOV_ENABLE_COMPARISONS -e DEBUG_FS -e DEBUG_KMEMLEAK -e DEBUG_INFO -e KALLSYMS -e KALLSYMS_ALL -e NAMESPACES -e UTS_NS -e IPC_NS -e PID_NS -e NET_NS -e CGROUP_PIDS -e MEMCG -e USER_NS -e CONFIGFS_FS -e SECURITYFS -e KASAN -e KASAN_INLINE -e FAULT_INJECTION -e FAULT_INJECTION_DEBUG_FS -e FAULT_INJECTION_USERCOPY -e FAILSLAB -e FAIL_PAGE_ALLOC -e FAIL_MAKE_REQUEST -e FAIL_IO_TIMEOUT -e FAIL_FUTEX -e LOCKDEP -e PROVE_LOCKING -e DEBUG_ATOMIC_SLEEP -e PROVE_RCU -e DEBUG_VM -e REFCOUNT_FULL -e FORTIFY_SOURCE -e HARDENED_USERCOPY -e LOCKUP_DETECTOR -e SOFTLOCKUP_DETECTOR -e HARDLOCKUP_DETECTOR -e BOOTPARAM_HARDLOCKUP_PANIC -e DETECT_HUNG_TASK -e WQ_WATCHDOG -e USB_GADGET -e USB_RAW_GADGET -e TUN -e KCSAN -d RANDOMIZE_BASE -e MAC80211_HWSIM -e IEEE802154 -e MAC802154 -e IEEE802154_DRIVERS -e IEEE802154_HWSIM -e BT -e BT_HCIVHCI > echo "CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=140" >> .config > echo "CONFIG_RCU_CPU_STALL_TIMEOUT=100" >> .config > > I will be happy to test any patch or provide any extra log if needed. > Though I am not sure how I will collect extra logs (if needed) as there > was no output from qemu. I see KASAN in your config, does this fix it? https://lore.kernel.org/lkml/166693938482.29415.7034851115705424459.tip-bot2@tip-bot2/ -- Kees Cook ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: boot failure of linux-next due to 1248fb6a8201 ("x86/mm: Randomize per-cpu entry area") 2022-10-28 16:41 ` Kees Cook @ 2022-10-28 20:04 ` Sudip Mukherjee 0 siblings, 0 replies; 5+ messages in thread From: Sudip Mukherjee @ 2022-10-28 20:04 UTC (permalink / raw) To: Kees Cook Cc: Peter Zijlstra, Dave Hansen, Thomas Gleixner, Ingo Molnar, Borislav Petkov, x86, H. Peter Anvin, Andy Lutomirski, linux-kernel, linux-next On Fri, Oct 28, 2022 at 5:41 PM Kees Cook <keescook@chromium.org> wrote: > > On Fri, Oct 28, 2022 at 02:29:14PM +0100, Sudip Mukherjee (Codethink) wrote: > > Hi All, > > > > Our qemu boots were failing since next-20221024, and a git bisect of > > next-20221028 showed the bad commit as 1248fb6a8201 ("x86/mm: Randomize per-cpu entry area") > > > > After reverting the commit I could boot qemu again with next-20221028. > > > > This is my config: > > > > make defconfig > > make kvm_guest.config > > scripts/config -e KCOV -e KCOV_INSTRUMENT_ALL -e KCOV_ENABLE_COMPARISONS -e DEBUG_FS -e DEBUG_KMEMLEAK -e DEBUG_INFO -e KALLSYMS -e KALLSYMS_ALL -e NAMESPACES -e UTS_NS -e IPC_NS -e PID_NS -e NET_NS -e CGROUP_PIDS -e MEMCG -e USER_NS -e CONFIGFS_FS -e SECURITYFS -e KASAN -e KASAN_INLINE -e FAULT_INJECTION -e FAULT_INJECTION_DEBUG_FS -e FAULT_INJECTION_USERCOPY -e FAILSLAB -e FAIL_PAGE_ALLOC -e FAIL_MAKE_REQUEST -e FAIL_IO_TIMEOUT -e FAIL_FUTEX -e LOCKDEP -e PROVE_LOCKING -e DEBUG_ATOMIC_SLEEP -e PROVE_RCU -e DEBUG_VM -e REFCOUNT_FULL -e FORTIFY_SOURCE -e HARDENED_USERCOPY -e LOCKUP_DETECTOR -e SOFTLOCKUP_DETECTOR -e HARDLOCKUP_DETECTOR -e BOOTPARAM_HARDLOCKUP_PANIC -e DETECT_HUNG_TASK -e WQ_WATCHDOG -e USB_GADGET -e USB_RAW_GADGET -e TUN -e KCSAN -d RANDOMIZE_BASE -e MAC80211_HWSIM -e IEEE802154 -e MAC802154 -e IEEE802154_DRIVERS -e IEEE802154_HWSIM -e BT -e BT_HCIVHCI > > echo "CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=140" >> .config > > echo "CONFIG_RCU_CPU_STALL_TIMEOUT=100" >> .config > > > > I will be happy to test any patch or provide any extra log if needed. > > Though I am not sure how I will collect extra logs (if needed) as there > > was no output from qemu. > > I see KASAN in your config, does this fix it? > > https://lore.kernel.org/lkml/166693938482.29415.7034851115705424459.tip-bot2@tip-bot2/ Yes, it does. Thanks. I can see qemu booting up again. Also, looks like thats already merged to x86/mm, so I am not sending a Tested-by in reply to that patch. -- Regards Sudip ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-10-28 20:05 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-28 13:29 boot failure of linux-next due to 1248fb6a8201 ("x86/mm: Randomize per-cpu entry area") Sudip Mukherjee (Codethink)
2022-10-28 14:33 ` Dave Hansen
2022-10-28 16:06 ` Sudip Mukherjee
2022-10-28 16:41 ` Kees Cook
2022-10-28 20:04 ` Sudip Mukherjee
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).