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 B8BC6EB64DD for ; Tue, 4 Jul 2023 06:05:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229971AbjGDGFV (ORCPT ); Tue, 4 Jul 2023 02:05:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43920 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229583AbjGDGFT (ORCPT ); Tue, 4 Jul 2023 02:05:19 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B9C5BCE; Mon, 3 Jul 2023 23:05:18 -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 365C16113B; Tue, 4 Jul 2023 06:05:18 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3B090C433C7; Tue, 4 Jul 2023 06:05:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1688450717; bh=19LKfZBc3Esf04ryoJNH2YTdCewnxeOCzfggqe7jPgc=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=r+J5n76ZlHfm+4z4MmLEe6JBVMDBOAMyr2F9P7wwAV9eZV2M5Ev7pHwgPWjBYL1Qp Wz6e4aVQE+qi2enJqRdK9VBFvlBQhNTfOt22mquuoFXmhWkH6xGfHwFYash/rasZP+ C6kPuaTLKut2InLqKr8I1eoARhaICoKGf5ATYWfOZ98GAGp0/CjE+qCTIzH0TP/vh9 lYawywwOSTC1MntXJuKYNb0aDMHT+rx5wghNssFStqjRROEwWp2UcSvZuIOolqc7Tt dOKtY3tO6A/tJPQzDRcu74fdIKaNoZ2sXA2vFN9Dz0lk6XYp8i0FRqo4bT9tDCTn+z uan7+J7bMvJ1Q== Message-ID: <3fde3786-24c8-1a03-bd35-5f83ee3474ba@kernel.org> Date: Tue, 4 Jul 2023 08:05:08 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: [PATCH] pstore/ram: Add support for dynamically allocated ramoops memory regions Content-Language: en-US To: Elliot Berman , Kees Cook , Isaac Manjarres , Kees Cook Cc: John Stultz , Tony Luck , "Guilherme G. Piccoli" , kernel-team@android.com, linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org, Trilok Soni , Satya Durga Srinivasu Prabhala , Mukesh Ojha References: <20230622005213.458236-1-isaacmanjarres@google.com> <202306212212.5E53607@keescook> <3A2CFB4D-27D0-4FEB-93B4-2F888305DE5A@kernel.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 22/06/2023 21:51, Elliot Berman wrote: >> Boot 1. >> Get address Foo. >> Crash, write to Foo. >> Boot 2. >> Get address Bar, different from Foo. >> Nothing found at Bar, so nothing populated in pstorefs; crash report from Boot 1 unavailable. >> >> I feel like there is something I don't understand about the Foo/Bar addresses in my example. >> > > I believe this is being added to support the QCOM SoC minidump feature. > Mukesh has posted it on the mailing lists here: > > https://lore.kernel.org/all/1683133352-10046-1-git-send-email-quic_mojha@quicinc.com/ > > https://lore.kernel.org/all/1683133352-10046-10-git-send-email-quic_mojha@quicinc.com/ And since this is coming bypassing DT maintainers and clearly against Rob's feedback so far, that's a no. > > Mukesh, could you comment whether this patch is wanted for us in the > version you have posted? It looks like maybe not based on the commit > text in patch #9. Best regards, Krzysztof