Return-Path: Received: from muru.com ([72.249.23.125]:57510 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726340AbeLKTMY (ORCPT ); Tue, 11 Dec 2018 14:12:24 -0500 Date: Tue, 11 Dec 2018 11:12:20 -0800 From: Tony Lindgren To: Chandan Rajendra , Theodore Ts'o Cc: Stephen Rothwell , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org Subject: Regression in next-20181211 with fsverity changes Message-ID: <20181211191220.GW6707@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: linux-ext4-owner@vger.kernel.org List-ID: Hi, Looks like commit 4de97efb578a ("fsverity: Move verity status check to fsverity_file_open") causes a boot regression for me with root on ext4 SDIO card, see below. Any ideas what goes wrong? Regards, Tony 8< ---------------------- Starting init: /bin/sh exists but couldn't execute it (error -95) Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. CPU1: stopping CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.20.0-rc6-next-20181211 #1080 Hardware name: Generic OMAP4 (Flattened Device Tree) [] (unwind_backtrace) from [] (show_stack+0x10/0x14) [] (show_stack) from [] (dump_stack+0xb0/0xe8) [] (dump_stack) from [] (handle_IPI+0x318/0x380) [] (handle_IPI) from [] (gic_handle_irq+0x94/0xa8) [] (gic_handle_irq) from [] (__irq_svc+0x70/0x98) Exception stack(0xee911ef8 to 0xee911f40) 1ee0: 00000001 00000001 1f00: 00000000 ee90a180 00000000 c0e13fc4 00000000 ef6afbb8 c0ec8830 de03d29f 1f20: 00000000 00000000 00000000 ee911f48 c01a4120 c06f8fb4 20000153 ffffffff [] (__irq_svc) from [] (cpuidle_enter_state+0x270/0x46c) [] (cpuidle_enter_state) from [] (cpuidle_enter_state_coupled+0x148/0x3e0) [] (cpuidle_enter_state_coupled) from [] (do_idle+0x234/0x2b8) [] (do_idle) from [] (cpu_startup_entry+0x18/0x1c) [] (cpu_startup_entry) from [<8010274c>] (0x8010274c) ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. ]---