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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E3DC9C433FE for ; Mon, 14 Nov 2022 14:55:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=MpDAFsw1dFg3pMUtpl1FoDRVY9SUk2XzBehnfhbUn6Q=; b=CNncEzC1yUza4V HoyZrbV/M6/TesUMmf8s60zOgutBhd148Ns0ZCT/4em1YcP4q7pwC/qxT6IKovHjpQ98s9RnmQ9Ce 6XlGW3nz+wSYyVaT3BAV2AIp3Gkifom8srsr05XNtzvORa9oitOnuGH5shHVRkFmuIWd2vLKonAQP JC4SkJvLdzwtfoBHXf232TT8e9LC0RwftlS96ytZo1wj/LTbMlxFkDg2b1Fray5KqRvCZWdV8Hua4 7Cw8i/PVTJpm8I7Dbt4XqOh9uEWbXc14EpLyCHSmpqSzR7cINSnoZCWXWL4zL2wbZt2NKeD9fBQZa zGX0JTnYolxITyhvvz6A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ouarG-001yyH-CS; Mon, 14 Nov 2022 14:54:47 +0000 Received: from ams.source.kernel.org ([2604:1380:4601:e00::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1ouar8-001yta-36 for linux-arm-kernel@lists.infradead.org; Mon, 14 Nov 2022 14:54:39 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id C1AB1B80FED; Mon, 14 Nov 2022 14:54:34 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id BA0E2C433D6; Mon, 14 Nov 2022 14:54:31 +0000 (UTC) Date: Mon, 14 Nov 2022 14:54:28 +0000 From: Catalin Marinas To: Will Deacon Cc: Manivannan Sadhasivam , Amit Pundir , Robin Murphy , Bjorn Andersson , Sibi Sankar , Linus Torvalds , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Dmitry Baryshkov Subject: Re: [GIT PULL] arm64 updates for 6.1-rc1 Message-ID: References: <20221005144116.2256580-1-catalin.marinas@arm.com> <20221111173952.GB5393@thinkpad> <20221111191820.GC5393@thinkpad> <20221114140903.GF30263@willie-the-truck> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20221114140903.GF30263@willie-the-truck> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221114_065438_322648_E39461B2 X-CRM114-Status: GOOD ( 15.89 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, Nov 14, 2022 at 02:09:04PM +0000, Will Deacon wrote: > On Sat, Nov 12, 2022 at 12:48:20AM +0530, Manivannan Sadhasivam wrote: > > I digged a little further and found that the crash was due to the secure > > processor (XPU) violation. It happens because, CPU tried acccessing the memory > > after sharing it with the modem for firmware metadata validation. [...] > > Sibi tried fixing this problem earlier by using a hack in the remoteproc driver > > [1], but I guess that got negated due to c44094eee32f? > > Performing a clean rather than a clean+invalidate when the buffer is > allocated (which is what is achieved by c44094eee32f) shouldn't affect > this afaict. I agree. The DMA_ATTR_NO_KERNEL_MAPPING used in the qcom_q6v5_mss fix only ensures that there is no non-cacheable DMA mapping but we still have the kernel linear map in place that may be accessed speculatively by the CPU at any point. I can't tell why the clean+inval makes any difference but I suspect it's a matter of time before you'd hit similar conditions again (maybe not at boot). -- Catalin _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel