From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Chen-Yu Tsai <wens@kernel.org>,
Samuel Holland <samuel@sholland.org>,
jaidevshastri@vt.edu
Cc: linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
Jaidev Shastri <jaidevshastri@vt.edu>
Subject: Re: [PATCH] soc: sunxi: sram: order the publication of base against sram_dev
Date: Sun, 27 Sep 2026 14:02:11 +0200 [thread overview]
Message-ID: <_KSVwOofQtuLLVcIRHSVdg@gmail.com> (raw)
In-Reply-To: <20260921-mb-sunxi-sram-v1-1-ad7817f0ee7d@vt.edu>
Dne torek, 22. september 2026 ob 02:48:49 Srednjeevropski poletni čas je Jaidev Shastri via B4 Relay napisal(a):
> From: Jaidev Shastri <jaidevshastri@vt.edu>
>
> sunxi_sram_claim() is called from the probe functions of the EMAC, the
> video engine and other consumers. It gates on the file-scope base
> pointer:
>
> if (!base)
> return -EPROBE_DEFER;
>
> and then walks sram_dev->of_node in sunxi_sram_of_parse().
Where do you see sunxi_sram_of_parse()? This function doesn't exist
in current kernel.
> sunxi_sram_probe() writes sram_dev and then base, both with plain
> stores, and the claimer reads both with plain loads. Neither the two
> stores nor the two loads are ordered, so a claimer on another CPU can
> pass the gate and dereference sram_dev == NULL.
>
> Keep the mapped registers in a local and publish base with
> smp_store_release() once sram_dev is set; read it with
> smp_load_acquire() in sunxi_sram_claim(). The error value is still
Where does sunxi_sram_claim() use sram_dev? It's used only in debugfs
show method.
I don't think this solves real issue, so NAK.
Best regards,
Jernej
> stored to base so that a failed probe keeps reporting it to claimers.
>
> Found with MBCheck, a static herd7-based memory consistency checker.
>
> Signed-off-by: Jaidev Shastri <jaidevshastri@vt.edu>
> ---
> drivers/soc/sunxi/sunxi_sram.c | 28 +++++++++++++++++++++-------
> 1 file changed, 21 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/soc/sunxi/sunxi_sram.c b/drivers/soc/sunxi/sunxi_sram.c
> index 2ccaeacf8..0e0b86ad3 100644
> --- a/drivers/soc/sunxi/sunxi_sram.c
> +++ b/drivers/soc/sunxi/sunxi_sram.c
> @@ -266,10 +266,14 @@ int sunxi_sram_claim(struct device *dev)
> int err;
> int count = 0;
>
> - if (IS_ERR(base))
> - return PTR_ERR(base);
> + void __iomem *regs;
>
> - if (!base)
> + /* Pairs with smp_store_release() in sunxi_sram_probe(). */
> + regs = smp_load_acquire(&base);
> + if (IS_ERR(regs))
> + return PTR_ERR(regs);
> +
> + if (!regs)
> return -EPROBE_DEFER;
>
> if (!dev || !dev->of_node)
> @@ -410,6 +414,7 @@ static int __init sunxi_sram_probe(struct platform_device *pdev)
> const struct sunxi_sramc_variant *variant;
> struct device *dev = &pdev->dev;
> struct regmap *regmap;
> + void __iomem *regs;
> int ret;
>
> sram_dev = &pdev->dev;
> @@ -420,12 +425,21 @@ static int __init sunxi_sram_probe(struct platform_device *pdev)
>
> dev_set_drvdata(dev, (struct sunxi_sramc_variant *)variant);
>
> - base = devm_platform_ioremap_resource(pdev, 0);
> - if (IS_ERR(base))
> - return PTR_ERR(base);
> + regs = devm_platform_ioremap_resource(pdev, 0);
> + if (IS_ERR(regs)) {
> + base = regs;
> + return PTR_ERR(regs);
> + }
> +
> + /*
> + * base is the gate that sunxi_sram_claim() tests before it walks
> + * sram_dev->of_node. Publish it after sram_dev so that a claimer on
> + * another CPU that passes the gate also sees sram_dev.
> + */
> + smp_store_release(&base, regs);
>
> if (variant->num_emac_clocks || variant->has_ldo_ctrl) {
> - regmap = devm_regmap_init_mmio(dev, base, &sunxi_sram_regmap_config);
> + regmap = devm_regmap_init_mmio(dev, regs, &sunxi_sram_regmap_config);
> if (IS_ERR(regmap))
> return PTR_ERR(regmap);
>
>
> ---
> base-commit: 93f51579e7df248780214094418f205253383cc5
> change-id: 20260921-mb-sunxi-sram-41c3288a4660
>
> Best regards,
> --
> Jaidev Shastri <jaidevshastri@vt.edu>
>
>
>
prev parent reply other threads:[~2026-09-27 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 0:48 Jaidev Shastri via B4 Relay
2026-09-27 12:02 ` Jernej Škrabec [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=_KSVwOofQtuLLVcIRHSVdg@gmail.com \
--to=jernej.skrabec@gmail.com \
--cc=jaidevshastri@vt.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=wens@kernel.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®