From: Bjorn Andersson <andersson@kernel.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
Sricharan Ramabadhran <quic_srichara@quicinc.com>,
Arun Kumar Neelakantam <quic_aneela@quicinc.com>,
Chunkai Deng <chunkai.deng@oss.qualcomm.com>
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 [thread overview]
Message-ID: <178405071413.579772.309823663334721744.b4-ty@kernel.org> (raw)
In-Reply-To: <20260618-rpmsg-glink-smem-mb-v1-1-68a026453a69@oss.qualcomm.com>
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 <andersson@kernel.org>
prev parent reply other threads:[~2026-07-14 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 7:16 Chunkai Deng
2026-06-29 12:36 ` Konrad Dybcio
2026-07-14 17:38 ` Bjorn Andersson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178405071413.579772.309823663334721744.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=chris.lew@oss.qualcomm.com \
--cc=chunkai.deng@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_aneela@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=stable@vger.kernel.org \
--cc=tony.truong@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®