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 C662EEB64DC for ; Wed, 19 Jul 2023 02:10:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229570AbjGSCKo (ORCPT ); Tue, 18 Jul 2023 22:10:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46984 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229437AbjGSCKj (ORCPT ); Tue, 18 Jul 2023 22:10:39 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D124E1FDB for ; Tue, 18 Jul 2023 19:10:23 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 63D38616C9 for ; Wed, 19 Jul 2023 02:10:23 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id B88ECC433B7; Wed, 19 Jul 2023 02:10:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1689732622; bh=/qxqKDN+VTBagSXNiDocGJj67ckmM0Hk3yG0wfM16Sw=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=QmCszSNljwNBeFtPHzBjA6a/ocdr6mO2IlwtPyONUV5ct47+6tVEcI5IAIe8wiEPb ReGzSbxV1BUJJkSLqOjDfY2QeQXx0cD6qExpS6pM3oURnAX4kVWGk/+AKwTUNNSCGP HmtpOD5gFWWPML9Z5Zc6MZzvBD1VP1iu7wK9LjphPZpGhS7sixjLq0RSQIXLvk2R5N ZP4Q80B4n+7kzT0ykag6YTNdrCIrZqK02hGimPl3Td8NwZTbaEQNKsL1KlnN8mvLuZ 1w/QFf6i8p/h8Xj6NVVpcfHn/boNJV9W2wcGvwfma/NzlmTjV2PmbNW1CJfX5P/VJ0 /9GYH4BE0vRJA== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id 9BFDDE22AE5; Wed, 19 Jul 2023 02:10:22 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PATCH] drivers/cros_ec: Emergency sync filesystem on EC panic From: patchwork-bot+chrome-platform@kernel.org Message-Id: <168973262262.24960.14264135195868218640.git-patchwork-notify@kernel.org> Date: Wed, 19 Jul 2023 02:10:22 +0000 References: <20230717232932.1.I361812b405bd07772f66660624188339ab158772@changeid> In-Reply-To: <20230717232932.1.I361812b405bd07772f66660624188339ab158772@changeid> To: Rob Barnes Cc: pmalani@chromium.org, chrome-platform@lists.linux.dev, briannorris@chromium.org, bleung@chromium.org, groeck@chromium.org, linux-kernel@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello: This patch was applied to chrome-platform/linux.git (for-next) by Tzung-Bi Shih : On Mon, 17 Jul 2023 23:29:32 +0000 you wrote: > Perform an emergency filesystem sync when an EC panic is reported. An > emergency sync actually performs two syncs internally in case some > inodes or pages are temporarily locked. > > hw_protection_shutdown is replaced for a few reasons. It is unnecessary > because the EC will force reset either way. hw_protection_shutdown does > not reliably sync filesystem before shutting down. emergency_sync is not > synchronous so hw_protection_shutdown may interrupt emergency_sync. > > [...] Here is the summary with links: - drivers/cros_ec: Emergency sync filesystem on EC panic https://git.kernel.org/chrome-platform/c/a6edd5f5d9cc You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html