From: sashiko-bot@kernel.org
To: "Manikandan Muralidharan" <manikandan.m@microchip.com>
Cc: "Richard Weinberger" <richard@nod.at>,
"Pratyush Yadav" <pratyush@kernel.org>,
robh@kernel.org, "Michael Walle" <mwalle@kernel.org>,
conor+dt@kernel.org, devicetree@vger.kernel.org,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"Takahiro Kuwano" <takahiro.kuwano@infineon.com>,
"Miquel Raynal" <miquel.raynal@bootlin.com>
Subject: Re: [PATCH v7 4/7] nvmem: layouts: add Microchip/SST SFDP EUI layout driver
Date: Thu, 13 Aug 2026 10:51:59 +0000 [thread overview]
Message-ID: <20260813105159.DBE771F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260812104955.485667-5-manikandan.m@microchip.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Unloading the `microchip-sst26vf-sfdp-eui` module leaves a dangling `read_post_process` function pointer in the NVMEM core, leading to a kernel panic when the cell is subsequently read.
--
--- Patch [4]: [PATCH v7 4/7] nvmem: layouts: add Microchip/SST SFDP EUI layout driver ---
commit ede7813294e82294452049f0c0c040524f47bb8e
Author: Manikandan Muralidharan <manikandan.m@microchip.com>
nvmem: layouts: add Microchip/SST SFDP EUI layout driver
This commit adds an NVMEM layout driver for Microchip/SST SFDP flashes.
It locates the vendor-specific parameter table at runtime and exposes the
EUI-48 identifier as an NVMEM cell to be used as a MAC address.
> diff --git a/drivers/nvmem/layouts/sst26vf-sfdp-eui.c b/drivers/nvmem/layouts/sst26vf-sfdp-eui.c
> new file mode 100644
> index 0000000000000..641318d6f0af6
> --- /dev/null
> +++ b/drivers/nvmem/layouts/sst26vf-sfdp-eui.c
[ ... ]
> +static int sfdp_eui_add_cells(struct nvmem_layout *layout)
> +{
[ ... ]
> + info.name = "mac-address";
> + info.offset = base + SFDP_MCHP_EUI48_OFFSET;
> + info.bytes = ETH_ALEN;
> + info.np = of_get_child_by_name(layout_np, "mac-address");
> + info.read_post_process = sfdp_eui_read_post_process;
> +
> + ret = nvmem_add_one_cell(nvmem, &info);
[Severity: High]
Does registering this read_post_process callback create a dangling pointer
when the module is unloaded?
[ ... ]
> +static void sfdp_eui_remove(struct nvmem_layout *layout)
> +{
> + nvmem_layout_unregister(layout);
> +}
[Severity: High]
Can unloading this module lead to a kernel panic?
Because nvmem_layout_unregister() is an empty stub in the NVMEM core, the
cells added by this layout are never removed.
If the module is unloaded, the sysfs entry for the cell remains active.
A subsequent read of the sysfs file will invoke the read_post_process
callback, which now points to freed module memory, causing a panic.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260812104955.485667-1-manikandan.m@microchip.com?part=4
next prev parent reply other threads:[~2026-08-13 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 10:49 [PATCH v7 0/7] Read MAC address from SST vendor specific SFDP region Manikandan Muralidharan
2026-08-12 10:49 ` [PATCH v7 1/7] dt-bindings: mtd: jedec,spi-nor: allow the SFDP to be exposed via NVMEM Manikandan Muralidharan
2026-08-12 10:49 ` [PATCH v7 2/7] dt-bindings: nvmem: layouts: add Microchip/SST SFDP EUI layout Manikandan Muralidharan
2026-08-12 10:49 ` [PATCH v7 3/7] mtd: spi-nor: sfdp: expose the SFDP as a read-only NVMEM device Manikandan Muralidharan
2026-08-13 10:52 ` sashiko-bot
2026-08-12 10:49 ` [PATCH v7 4/7] nvmem: layouts: add Microchip/SST SFDP EUI layout driver Manikandan Muralidharan
2026-08-13 10:51 ` sashiko-bot [this message]
2026-08-12 10:49 ` [PATCH v7 5/7] ARM: dts: microchip: sama5d27_wlsom1: use fixed-partitions for QSPI flash Manikandan Muralidharan
2026-08-13 10:51 ` sashiko-bot
2026-08-12 10:49 ` [PATCH v7 6/7] ARM: dts: microchip: sama5d27_wlsom1: read MAC address from QSPI SFDP Manikandan Muralidharan
2026-08-12 10:49 ` [PATCH v7 7/7] ARM: configs: sama5: enable Microchip/SST SFDP EUI NVMEM layout Manikandan Muralidharan
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=20260813105159.DBE771F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=manikandan.m@microchip.com \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=takahiro.kuwano@infineon.com \
--cc=vigneshr@ti.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