diff options
| author | Ioana Ciornei <[email protected]> | 2025-04-08 10:58:10 +0000 |
|---|---|---|
| committer | Christophe Leroy <[email protected]> | 2025-05-12 23:34:57 +0000 |
| commit | dd7d8e012b23de158ca0188239c7a1f2a83b4484 (patch) | |
| tree | 71858bd6b210fe07ea1d33dfbe9f75396b1073cb /scripts/gcc-plugins/sancov_plugin.c | |
| parent | bus: fsl-mc: fix double-free on mc_dev (diff) | |
| download | kernel-dd7d8e012b23de158ca0188239c7a1f2a83b4484.tar.gz kernel-dd7d8e012b23de158ca0188239c7a1f2a83b4484.zip | |
bus: fsl-mc: do not add a device-link for the UAPI used DPMCP device
The fsl-mc bus associated to the root DPRC in a DPAA2 system exports a
device file for userspace access to the MC firmware. In case the DPRC's
local MC portal (DPMCP) is currently in use, a new DPMCP device is
allocated through the fsl_mc_portal_allocate() function.
In this case, the call to fsl_mc_portal_allocate() will fail with -EINVAL
when trying to add a device link between the root DPRC (consumer) and
the newly allocated DPMCP device (supplier). This is because the DPMCP
is a dependent of the DPRC device (the bus).
Fix this by not adding a device link in case the DPMCP is allocated for
the root DPRC's usage.
Fixes: afb77422819f ("bus: fsl-mc: automatically add a device_link on fsl_mc_[portal,object]_allocate")
Signed-off-by: Ioana Ciornei <[email protected]>
Cc: [email protected]
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Christophe Leroy <[email protected]>
Diffstat (limited to 'scripts/gcc-plugins/sancov_plugin.c')
0 files changed, 0 insertions, 0 deletions
