From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C98784156CA; Tue, 14 Jul 2026 17:38:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784050724; cv=none; b=kVfkCn4B+42zrCBZ+nTDvx0NPmHGpHwBEuapPaS/BSHa12o3TMHUCgddGKg6gb/3lsSE0sdAry7XV0YOUfw63uDBewlCFGdZd4CSY9JetqN6Vei0t6R1L+K/Dxy93TTLTBD50iuQ36FYSoKR2D8loGqwGcEhXhbdOLtY99rGoN4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784050724; c=relaxed/simple; bh=zlQ4hvLyjJrGJUqDvU2bRRy6UPS2rq+BC6SkHKiLDzg=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=rXSEBvWuudYQ55EwK3thzamw9WAVFEO8rNZYWiFAJGp/77ve8TP14lpkZ/R2fplSX0WN22elL0Vf+IEtW2QtRXaVkhlR6QavnDQBxDqZKswcOW+a+GcxbI9QrJphagVBbdBp05oJAphcj38lc4EY9Y/ehdM4PvvxmTG90OKRLRs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=j5eH6/d/; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="j5eH6/d/" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 381941F000E9; Tue, 14 Jul 2026 17:38:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1784050722; bh=fTSbvsyD1arNaZtplNUn+GJJgVbQsY+rgW72a3TM5kw=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=j5eH6/d/ahxQUzjNwLjmS1amL2N9eb4Fm3wTJODEBmi+3Qwk/aZzwoIWo1DPlGO2x 0BUPu9MEXLveNRrc/Jd+9bBOpc8Q0jB8VaaSupVSR0v/6fl3AkVXbK2nUZWOLhS5Kb r2I4PbShct32tHYwDCtO4NL/7bd2wG60UMlY5oazwBMleOCYhDUGLGfazuGhHs0v0A Uih4vWyUnDRvocXqa8Yj4BzPp95F2zK2ZUB3zb9MK3wDlxYJj0tT22c/42lbbo233b ZQa1p73jkZOOVbBbvTtnjlTRH1k8NHMdbvRTp9pE4/z7MilvLhZ+/y5PdM4atVLHO/ j7HPtRGN2cIag== From: Bjorn Andersson To: Mathieu Poirier , Sricharan Ramabadhran , Arun Kumar Neelakantam , Chunkai Deng Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, konrad.dybcio@oss.qualcomm.com, tony.truong@oss.qualcomm.com, chris.lew@oss.qualcomm.com, stable@vger.kernel.org Subject: Re: [PATCH] rpmsg: glink: smem: order FIFO read after availability check Date: Tue, 14 Jul 2026 12:38:36 -0500 Message-ID: <178405071413.579772.309823663334721744.b4-ty@kernel.org> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20260618-rpmsg-glink-smem-mb-v1-1-68a026453a69@oss.qualcomm.com> References: <20260618-rpmsg-glink-smem-mb-v1-1-68a026453a69@oss.qualcomm.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit On Thu, 18 Jun 2026 00:16:39 -0700, Chunkai Deng wrote: > glink_smem_rx_peek() reads the RX FIFO payload after the caller has > determined data is available via glink_smem_rx_avail(), which reads the > remote-updated head index. A control dependency between the head read > and the subsequent payload read does not order the two loads, so the > CPU may speculatively read the FIFO before observing the head update > and consume stale data the remote has not yet published. > > [...] Applied, thanks! [1/1] rpmsg: glink: smem: order FIFO read after availability check commit: 786439ad58763e04b91bc2ec5f590e463939f197 Best regards, -- Bjorn Andersson