From: Kevin Traynor <ktraynor@redhat.com>
To: David Marchand <david.marchand@redhat.com>, dev@dpdk.org
Cc: stable@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>,
Sachin Saxena <sachin.saxena@nxp.com>,
Rohit Raj <rohit.raj@nxp.com>
Subject: Re: [PATCH 2/8] bus/fslmc: fix bus cleanup
Date: Mon, 23 Mar 2026 16:59:35 +0000 [thread overview]
Message-ID: <0b33ca24-dce4-47f2-aacd-cb0e9ecfd5d6@redhat.com> (raw)
In-Reply-To: <20260323105306.1531689-3-david.marchand@redhat.com>
On 3/23/26 10:52 AM, David Marchand wrote:
> The close operation was never closing probed devices.
>
> Taking a step back, reevaluating the devargs makes no sense during the
> close step, as a probed device must have passed the allow/block list
> evaluation initially.
>
> Since the device contains a reference to the driver that probed it,
> simply call this driver remove op.
>
> Fixes: 274fd921ff7f ("bus/fslmc: support close operation")
> Cc: stable@dpdk.org
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> drivers/bus/fslmc/fslmc_vfio.c | 21 ++++-----------------
> 1 file changed, 4 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/bus/fslmc/fslmc_vfio.c b/drivers/bus/fslmc/fslmc_vfio.c
> index 550d4e0e8d..7daa18d850 100644
> --- a/drivers/bus/fslmc/fslmc_vfio.c
> +++ b/drivers/bus/fslmc/fslmc_vfio.c
> @@ -1393,7 +1393,7 @@ fslmc_close_iodevices(struct rte_dpaa2_device *dev,
> {
> struct rte_dpaa2_object *object = NULL;
> struct rte_dpaa2_driver *drv;
> - int ret, probe_all;
> + int ret;
>
> switch (dev->dev_type) {
> case DPAA2_IO:
> @@ -1411,22 +1411,9 @@ fslmc_close_iodevices(struct rte_dpaa2_device *dev,
> case DPAA2_ETH:
> case DPAA2_CRYPTO:
> case DPAA2_QDMA:
> - probe_all = rte_fslmc_bus.bus.conf.scan_mode !=
> - RTE_BUS_SCAN_ALLOWLIST;
> - TAILQ_FOREACH(drv, &rte_fslmc_bus.driver_list, next) {
> - if (drv->drv_type != dev->dev_type)
> - continue;
> - if (rte_dev_is_probed(&dev->device))
> - continue;
> - if (probe_all ||
> - (dev->device.devargs &&
> - dev->device.devargs->policy ==
> - RTE_DEV_ALLOWED)) {
> - ret = drv->remove(dev);
> - if (ret)
> - DPAA2_BUS_ERR("Unable to remove");
> - }
> - }
> + drv = dev->driver;
> + if (drv && drv->remove && drv->remove(dev))
Not new but dpaa2_qdma_remove doesn't return an error which seems like a
bug, but it has it's own log and it's just a log here anyway, so not
critical.
> + DPAA2_BUS_ERR("Unable to remove");
> break;
> default:
> break;
next prev parent reply other threads:[~2026-03-23 16:59 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 10:52 [PATCH 0/8] Rework device probing David Marchand
2026-03-23 10:52 ` [PATCH 1/8] devtools: check packet forwarding in null test David Marchand
2026-03-23 10:52 ` [PATCH 2/8] bus/fslmc: fix bus cleanup David Marchand
2026-03-23 16:59 ` Kevin Traynor [this message]
2026-03-26 8:22 ` David Marchand
2026-03-26 8:49 ` Kevin Traynor
2026-03-24 5:15 ` Hemant Agrawal
2026-03-24 5:15 ` Hemant Agrawal
2026-03-23 10:52 ` [PATCH 3/8] drivers/bus: require probe function for NXP drivers David Marchand
2026-03-23 16:59 ` Kevin Traynor
2026-03-24 5:15 ` Hemant Agrawal
2026-03-23 10:52 ` [PATCH 4/8] drivers: cleanup devargs lookup in bus scan David Marchand
2026-03-24 5:16 ` Hemant Agrawal
2026-03-24 14:13 ` Kevin Traynor
2026-03-24 16:10 ` Stephen Hemminger
2026-03-23 10:52 ` [PATCH 5/8] bus: factorize devargs lookup David Marchand
2026-03-24 14:16 ` Kevin Traynor
2026-03-24 16:11 ` Stephen Hemminger
2026-03-23 10:53 ` [PATCH 6/8] bus: factorize device selection David Marchand
2026-03-24 14:15 ` Kevin Traynor
2026-03-26 8:48 ` David Marchand
2026-03-24 16:12 ` Stephen Hemminger
2026-03-23 10:53 ` [PATCH 7/8] bus: remove per bus scan mode David Marchand
2026-03-24 16:02 ` Kevin Traynor
2026-03-24 16:27 ` Kevin Traynor
2026-03-26 8:54 ` David Marchand
2026-03-23 10:53 ` [PATCH 8/8] eal: configure initial device probing David Marchand
2026-03-25 10:57 ` Kevin Traynor
2026-03-24 5:17 ` [PATCH 0/8] Rework " Hemant Agrawal
2026-03-25 15:22 ` Maxime Leroy
2026-03-26 10:24 ` [PATCH v2 0/7] " David Marchand
2026-03-26 10:24 ` [PATCH v2 1/7] devtools: check packet forwarding in null test David Marchand
2026-03-26 10:24 ` [PATCH v2 2/7] bus/fslmc: fix bus cleanup David Marchand
2026-03-26 11:50 ` Kevin Traynor
2026-03-26 10:24 ` [PATCH v2 3/7] drivers/bus: require probe function for NXP drivers David Marchand
2026-03-26 10:24 ` [PATCH v2 4/7] drivers: cleanup devargs lookup in bus scan David Marchand
2026-03-28 3:13 ` fengchengwen
2026-03-26 10:24 ` [PATCH v2 5/7] bus: factorize devargs lookup David Marchand
2026-03-26 11:51 ` Kevin Traynor
2026-03-28 3:33 ` fengchengwen
2026-04-03 14:22 ` David Marchand
2026-03-26 10:24 ` [PATCH v2 6/7] bus: factorize device selection David Marchand
2026-03-26 11:52 ` Kevin Traynor
2026-03-28 3:38 ` fengchengwen
2026-03-26 10:24 ` [PATCH v2 7/7] eal: configure initial device probing David Marchand
2026-03-28 4:00 ` fengchengwen
2026-04-03 14:25 ` David Marchand
2026-04-07 11:52 ` [PATCH v3 0/7] Rework " David Marchand
2026-04-07 11:52 ` [PATCH v3 1/7] devtools: check packet forwarding in null test David Marchand
2026-04-07 11:52 ` [PATCH v3 2/7] bus/fslmc: fix bus cleanup David Marchand
2026-04-07 11:52 ` [PATCH v3 3/7] drivers/bus: require probe function for NXP drivers David Marchand
2026-04-07 11:52 ` [PATCH v3 4/7] drivers/bus: cleanup devargs lookup in scan David Marchand
2026-04-07 11:52 ` [PATCH v3 5/7] bus: factorize devargs lookup David Marchand
2026-04-08 1:18 ` fengchengwen
2026-04-07 11:52 ` [PATCH v3 6/7] bus: factorize device selection David Marchand
2026-04-07 11:52 ` [PATCH v3 7/7] eal: configure initial device probing David Marchand
2026-04-08 1:44 ` fengchengwen
2026-04-07 11:58 ` [PATCH v3 0/7] Rework " David Marchand
2026-04-07 15:12 ` Stephen Hemminger
2026-04-10 14:34 ` Morten Brørup
2026-04-10 15:16 ` Kevin Traynor
2026-04-10 17:37 ` Stephen Hemminger
2026-04-10 21:13 ` [EXTERNAL] " Long Li
2026-04-10 22:50 ` Stephen Hemminger
2026-04-11 7:30 ` Morten Brørup
2026-04-11 10:10 ` David Marchand
2026-04-11 10:23 ` David Marchand
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=0b33ca24-dce4-47f2-aacd-cb0e9ecfd5d6@redhat.com \
--to=ktraynor@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=rohit.raj@nxp.com \
--cc=sachin.saxena@nxp.com \
--cc=stable@dpdk.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