From: "Arnd Bergmann" <arnd@arndb.de>
To: "Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Peter Griffin" <peter.griffin@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
jyescas@google.com, kernel-team@android.com,
stable@vger.kernel.org
Subject: Re: [PATCH v5 4/7] firmware: samsung: acpm: Add memory barrier before advancing RX pointer
Date: Fri, 29 May 2026 13:44:16 +0200 [thread overview]
Message-ID: <9d6bda31-839b-4cf8-b715-0d24760c73c2@app.fastmail.com> (raw)
In-Reply-To: <ed771a16-6241-4246-976e-48349e544b5b@linaro.org>
On Fri, May 29, 2026, at 13:20, Tudor Ambarus wrote:
> On 5/29/26 11:25 AM, Arnd Bergmann wrote:
>
> I missed the data dependency chain. I focused too much on the read
> part in __ioread32_copy() that I missed the RAM store implications
> in it. The RAM store is forced to wait for its SRAM load, and the
> writel is forced to wait for all the RAM stores. So the entire
> payload is guaranteed to be visible in memory RAM before the writel.
>
> Maybe I thought about the reordering of the final __raw_readl() loop
> iteration with the writel(). But the dma_wmb() -> __dma_wmb() ->
> dmb(oshst) from writel has a compiler barrier, so the compiler can't
> reorder the code. And given the ARM64 device memory accesses ordering,
> the ordering is protected.
Ok, thanks for checking and confirming my thoughts.
> My bad, sorry. We shall either drop or revert the patch. Please let
> me know if you prefer a revert.
I'll leave it up to Krzysztof, as he's already sent it to
soc@lists.linux.dev as part of the 7.1 fixes, and I'd
like to send the rest to Linus soon.
Krzysztof, if you can send an updated pull request without
this patch (and maybe also without b4a38606991c ("firmware:
samsung: acpm: Fix dummy stubs to return ERR_PTR"), see
separate email), I'll just merge the other fixes and
send that off instead.
Arnd
next prev parent reply other threads:[~2026-05-29 11:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 13:12 [PATCH v5 0/7] firmware: samsung: acpm: Various fixes for sashiko bug reports Tudor Ambarus
2026-05-05 13:12 ` [PATCH v5 1/7] firmware: samsung: acpm: Fix cross-thread RX length corruption Tudor Ambarus
2026-05-06 15:17 ` Alexey Klimov
2026-05-14 16:55 ` Krzysztof Kozlowski
2026-05-05 13:12 ` [PATCH v5 2/7] firmware: samsung: acpm: Fix mailbox channel leak on probe error Tudor Ambarus
2026-05-05 13:13 ` [PATCH v5 3/7] firmware: samsung: acpm: Fix dummy stubs to return ERR_PTR Tudor Ambarus
2026-05-29 11:51 ` Arnd Bergmann
2026-05-29 12:09 ` Krzysztof Kozlowski
2026-05-29 12:37 ` Tudor Ambarus
2026-05-29 13:38 ` Arnd Bergmann
2026-05-05 13:13 ` [PATCH v5 4/7] firmware: samsung: acpm: Add memory barrier before advancing RX pointer Tudor Ambarus
2026-05-28 17:44 ` Arnd Bergmann
2026-05-29 7:47 ` Krzysztof Kozlowski
2026-05-29 8:25 ` Arnd Bergmann
2026-05-29 11:20 ` Tudor Ambarus
2026-05-29 11:44 ` Arnd Bergmann [this message]
2026-05-29 12:10 ` Krzysztof Kozlowski
2026-05-05 13:13 ` [PATCH v5 5/7] firmware: samsung: acpm: Fix false timeouts and Use-After-Free in polling Tudor Ambarus
2026-05-05 13:13 ` [PATCH v5 6/7] firmware: samsung: acpm: Fix missing LKMM barriers in sequence allocator Tudor Ambarus
2026-05-05 13:13 ` [PATCH v5 7/7] firmware: samsung: acpm: Fix infinite loop on sequence number exhaustion Tudor Ambarus
2026-05-06 8:29 ` [PATCH v5 0/7] firmware: samsung: acpm: Various fixes for sashiko bug reports Tudor Ambarus
2026-05-14 16:56 ` Krzysztof Kozlowski
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=9d6bda31-839b-4cf8-b715-0d24760c73c2@app.fastmail.com \
--to=arnd@arndb.de \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=jyescas@google.com \
--cc=kernel-team@android.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=stable@vger.kernel.org \
--cc=tudor.ambarus@linaro.org \
/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®