patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Min Hu <humin29@huawei.com>
Cc: dev@dpdk.org, Huisong Li <lihuisong@huawei.com>,
	stable@dpdk.org, Gaetan Rivet <gaetan.rivet@6wind.com>
Subject: Re: [PATCH 1/2] bus/pci: fix a segfault when call callback
Date: Tue, 07 Jun 2022 19:38:07 +0200	[thread overview]
Message-ID: <27279391.ouqheUzb2q@thomas> (raw)
In-Reply-To: <20220521070523.34983-2-humin29@huawei.com>

21/05/2022 09:05, Min Hu (Connor):
> From: Huisong Li <lihuisong@huawei.com>
> 
> After the driver probe is executed, the callback in application will
> be called. The callback in application may call some APIs which access the

What is the "callback in application" ?
Do you mean the callback on probing event like RTE_ETH_EVENT_NEW?

> rte_pci_driver::driver by the device::driver pointer to get driver
> information. If the rte_pci_device::device::driver pointer isn't pointed to
> rte_pci_driver::driver in rte_pci_probe_one_driver, a segfault will occur.
> For example, when ethdev driver probe completes, the callback in
> application call rte_eth_dev_info_get which use dev->device->driver->name.
> So rte_pci_device::device::driver should point to rte_pci_driver::driver
> before executing the driver probe.

I understand the need and I approve the move.

> Fixes: c752998b5e2e ("pci: introduce library and driver")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
> ---
>  drivers/bus/pci/pci_common.c | 13 +++++++++++--
>  1 file changed, 11 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/bus/pci/pci_common.c b/drivers/bus/pci/pci_common.c
> index 4a3a87f24f..507a654779 100644
> --- a/drivers/bus/pci/pci_common.c
> +++ b/drivers/bus/pci/pci_common.c
> @@ -265,11 +265,22 @@ rte_pci_probe_one_driver(struct rte_pci_driver *dr,
>  			dr->driver.name, dev->id.vendor_id, dev->id.device_id,
>  			loc->domain, loc->bus, loc->devid, loc->function,
>  			dev->device.numa_node);
> +
> +	/*
> +	 * After the driver probe is executed, the callback in application will
> +	 * be called. The callback in application may call some APIs which use
> +	 * dev->device.driver to get some driver information. If the driver
> +	 * pointer isn't pointed to driver->driver here, a segfault will occur.
> +	 */

I would like to make this comment simpler
once I'm sure we share the same understanding.

> +	if (!already_probed)
> +		dev->device.driver = &dr->driver;
> +
>  	/* call the driver probe() function */
>  	ret = dr->probe(dr, dev);
>  	if (already_probed)
>  		return ret; /* no rollback if already succeeded earlier */
>  	if (ret) {
> +		dev->device.driver = NULL;
>  		dev->driver = NULL;
>  		if ((dr->drv_flags & RTE_PCI_DRV_NEED_MAPPING) &&
>  			/* Don't unmap if device is unsupported and
> @@ -282,8 +293,6 @@ rte_pci_probe_one_driver(struct rte_pci_driver *dr,
>  		dev->vfio_req_intr_handle = NULL;
>  		rte_intr_instance_free(dev->intr_handle);
>  		dev->intr_handle = NULL;
> -	} else {
> -		dev->device.driver = &dr->driver;
>  	}
>  
>  	return ret;
> 






  reply	other threads:[~2022-06-07 17:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220521070523.34983-1-humin29@huawei.com>
2022-05-21  7:05 ` Min Hu (Connor)
2022-06-07 17:38   ` Thomas Monjalon [this message]
2022-05-21  7:05 ` [PATCH 2/2] bus/vdev: " Min Hu (Connor)

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=27279391.ouqheUzb2q@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=gaetan.rivet@6wind.com \
    --cc=humin29@huawei.com \
    --cc=lihuisong@huawei.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;
as well as URLs for NNTP newsgroup(s).