FYI, we noticed the following commit: commit: bc1a405b009b69c8f86a6741614a503400a01f27 ("llist: Don't reinvent the wheel but use existing llist API") https://github.com/0day-ci/linux Byungchul-Park/llist-Don-t-reinvent-the-wheel-but-use-existing-llist-API/20170213-124427 in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -m 420M caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace): +------------------------------------------------+---------------+------------+ | | next-20170210 | bc1a405b00 | +------------------------------------------------+---------------+------------+ | boot_successes | 2 | 0 | | boot_failures | 0 | 16 | | Kernel_panic-not_syncing:No_working_init_found | 0 | 16 | +------------------------------------------------+---------------+------------+ [ 6.339828] Write protecting the kernel read-only data: 20480k [ 6.341283] Freeing unused kernel memory: 1040K [ 6.342591] Freeing unused kernel memory: 336K [ 6.343088] Failed to execute /init (error -26) [ 6.343598] Starting init: /bin/sh exists but couldn't execute it (error -26) [ 6.344335] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. [ 6.345783] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.10.0-rc7-next-20170210-00001-gbc1a405 #17 [ 6.346645] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.9.3-20161025_171302-gandalf 04/01/2014 [ 6.347642] Call Trace: [ 6.347887] dump_stack+0x61/0x7e [ 6.348236] ? rest_init+0x27/0xb9 [ 6.348315] panic+0xd3/0x20a [ 6.348315] ? rest_init+0xb9/0xb9 [ 6.348315] kernel_init+0xe2/0xe6 [ 6.348315] ret_from_fork+0x2c/0x40 [ 6.348315] Kernel Offset: disabled Elapsed time: 10 initrds=( To reproduce: git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git cd lkp-tests bin/lkp qemu -k <bzImage> job-script # job-script is attached in this email Thanks, Xiaolong