From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 46E84E95A8E for ; Mon, 9 Oct 2023 14:00:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1376852AbjJIOAl (ORCPT ); Mon, 9 Oct 2023 10:00:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44912 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1376693AbjJIOAj (ORCPT ); Mon, 9 Oct 2023 10:00:39 -0400 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A77249C for ; Mon, 9 Oct 2023 07:00:38 -0700 (PDT) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 33379C433C8; Mon, 9 Oct 2023 14:00:37 +0000 (UTC) Date: Mon, 9 Oct 2023 10:01:55 -0400 From: Steven Rostedt To: Joel Fernandes Cc: "Eric W. Biederman" , linux-kernel@vger.kernel.org, Ricardo Ribalda , Ross Zwisler , Rob Clark , Linus Torvalds , kexec@lists.infradead.org Subject: Re: [PATCH] kexec: Fix reboot race during device_shutdown() Message-ID: <20231009100155.6d71490f@gandalf.local.home> In-Reply-To: References: <20230929021213.2364883-1-joel@joelfernandes.org> <87bkdl55qm.fsf@email.froward.int.ebiederm.org> X-Mailer: Claws Mail 3.19.1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 7 Oct 2023 21:30:42 -0400 Joel Fernandes wrote: > Just checking how we want to proceed, is the consensus that we should > prevent kernel crashes without relying on userspace stopping all > processes? Should we fix regular reboot syscall as well and not just > kexec reboot? If you can show that we can trigger the crash on normal reboot, then I don't see why not. That is, if you have a program that does the reboot (without the SIGSTOP/SIGKILL calls) and triggers this crash, I think that's a legitimate reason to fix it on normal reboot too. -- Steve