DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ivan Malov <ivan.malov@arknetworks.am>
To: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
Cc: stephen@networkplumber.org, thomas@monjalon.net,
	ferruh.yigit@amd.com,  andrew.rybchenko@oktetlabs.ru,
	dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] [PATCH v3] lib/ethdev: fix segfault in secondary process by validating dev_private pointer
Date: Wed, 23 Jul 2025 17:19:25 +0400 (+04)	[thread overview]
Message-ID: <0792a0e5-dbbf-f3bc-527b-2fe7d33e8822@arknetworks.am> (raw)
In-Reply-To: <20250723131049.1703172-1-14pwcse1224@uetpeshawar.edu.pk>

Hi Khadem,

On Wed, 23 Jul 2025, Khadem Ullah wrote:

> In secondary processes, directly accessing 'dev->data->dev_private' can
> cause a segmentation fault if the primary process has exited or if the
> shared memory is no longer accessible.
>
> Secondary application not only breaking on device closing,
> but also getting segfault when we do "show device info all" from secondary
> after primary closes.
>
> This patch adds safety checks while using rte_mem_virt2phy(), with an
> unlikely() branch hint to minimize performance impact in the fast path.
> This ensures 'dev_private' is still valid before accessing it.
>
> Fixes: bdad90d12ec8 ("ethdev: change device info get callback to return int")
> Cc: stable@dpdk.org
>
> Signed-off-by: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
> ---
> lib/ethdev/rte_ethdev.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/lib/ethdev/rte_ethdev.c b/lib/ethdev/rte_ethdev.c
> index dd7c00bc94..343e156a4f 100644
> --- a/lib/ethdev/rte_ethdev.c
> +++ b/lib/ethdev/rte_ethdev.c
> @@ -4079,6 +4079,13 @@ rte_eth_dev_info_get(uint16_t port_id, struct rte_eth_dev_info *dev_info)
>
> 	if (dev->dev_ops->dev_infos_get == NULL)
> 		return -ENOTSUP;
> +	if (rte_eal_process_type() == RTE_PROC_SECONDARY &&
> +		unlikely(rte_mem_virt2phy(dev->data->dev_private) == RTE_BAD_PHYS_ADDR)) {
> +			RTE_ETHDEV_LOG_LINE(ERR,
> +			"Secondary: dev_private not accessible (primary exited?)");
> +			rte_errno = ENODEV;
> +			return -rte_errno;
> +	}
> 	diag = dev->dev_ops->dev_infos_get(dev, dev_info);
> 	if (diag != 0) {
> 		/* Cleanup already filled in device information */
> @@ -4307,7 +4314,13 @@ rte_eth_macaddr_get(uint16_t port_id, struct rte_ether_addr *mac_addr)
> 			port_id);
> 		return -EINVAL;
> 	}
> -
> +	if (rte_eal_process_type() == RTE_PROC_SECONDARY &&
> +		(dev->data->mac_addrs == NULL)) {
> +			RTE_ETHDEV_LOG_LINE(ERR,
> +			"Secondary: dev_private not accessible (primary exited?)");
> +			rte_errno = ENODEV;
> +			return -rte_errno;
> +	}
> 	rte_ether_addr_copy(&dev->data->mac_addrs[0], mac_addr);
>
> 	rte_eth_trace_macaddr_get(port_id, mac_addr);

I see one more API has been augmented with the check. But community members may
still argue this is not robust, as many other APIs will also fail. So, even if
the task was to augment as many APIs as possible with the check, then the check
would still be required to be factorised/generalised somehow. What do you think?

Please also note that there are already macro invocations in many of these APIs,
for example, RTE_ETH_VALID_PORTID_OR_ERR_RET. Could be convenient.

Thank you.

> -- 
> 2.43.0
>
>

  reply	other threads:[~2025-07-23 13:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 11:54 [PATCH] " Khadem Ullah
2025-07-22 13:39 ` Stephen Hemminger
2025-07-22 14:30   ` Khadem Ullah
2025-07-22 15:42     ` Stephen Hemminger
2025-07-22 16:01       ` Khadem Ullah
2025-07-22 16:13         ` Bruce Richardson
2025-07-22 17:04           ` Khadem Ullah
2025-07-22 17:38             ` Stephen Hemminger
2025-07-22 17:53               ` Khadem Ullah
2025-07-22 18:21                 ` Stephen Hemminger
2025-07-22 19:03                   ` Khadem Ullah
2025-07-22 19:05                   ` Ivan Malov
2025-07-22 22:28                     ` Stephen Hemminger
2025-07-23  4:29 ` Khadem Ullah
2025-07-23  4:50 ` [PATCH v2] " Khadem Ullah
2025-07-23 12:19   ` Khadem Ullah
2025-07-23 13:13     ` Khadem Ullah
2025-07-23 13:24       ` Ivan Malov
2025-07-23 13:26         ` Khadem Ullah
2025-07-23 13:31           ` Ivan Malov
2025-07-23 13:10   ` [PATCH] [PATCH v3] " Khadem Ullah
2025-07-23 13:19     ` Ivan Malov [this message]
2025-07-23 13:34       ` Khadem Ullah
2025-07-23 14:22         ` Stephen Hemminger
2025-07-23 14:21   ` [PATCH v2] " Stephen Hemminger

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=0792a0e5-dbbf-f3bc-527b-2fe7d33e8822@arknetworks.am \
    --to=ivan.malov@arknetworks.am \
    --cc=14pwcse1224@uetpeshawar.edu.pk \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).