From: Stephen Hemminger <stephen@networkplumber.org>
To: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
Cc: dev@dpdk.org, rasland@nvidia.com, stable@dpdk.org
Subject: Re: [PATCH] net/mlx5: fix crash when secondary queries dev info after primary exits
Date: Tue, 29 Jul 2025 14:46:11 -0700 [thread overview]
Message-ID: <20250729144611.46078d65@hermes.local> (raw)
In-Reply-To: <20250721073851.963141-1-14pwcse1224@uetpeshawar.edu.pk>
On Mon, 21 Jul 2025 03:38:51 -0400
Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk> wrote:
> When the primary process exits, the shared mlx5 state becomes
> unavailable to secondary processes. If a secondary process attempts
> to query device information (e.g., via testpmd), a NULL dereference
> may occur due to missing shared data.
>
> This patch adds a check for shared context availability and fails
> gracefully while preventing a crash.
>
> Fixes: e60fbd5b24fc ("mlx5: add device configure/start/stop")
> Cc: stable@dpdk.org
>
> Signed-off-by: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
> ---
NAK
As per other thread. Drivers need not worry about this.
If secondary gets to this point it is using freed bus and device information
and nothing is valid.
prev parent reply other threads:[~2025-07-29 21:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 7:38 Khadem Ullah
2025-07-21 10:58 ` Dariusz Sosnowski
2025-07-21 11:38 ` [PATCH] net/mlx5: fix crash when using meter in transfer flow Khadem Ullah
2025-07-21 11:46 ` [PATCH] net/mlx5: fix crash when secondary queries dev info after primary exits Ivan Malov
2025-07-21 11:59 ` Thomas Monjalon
2025-07-21 14:01 ` Dariusz Sosnowski
2025-07-22 12:14 ` [PATCH] ethdev: add dev_private check for secondary process Khadem Ullah
2025-07-22 16:26 ` [PATCH] net/mlx5: fix crash when secondary queries dev info after primary exits Ivan Malov
2025-07-22 16:52 ` Khadem Ullah
2025-07-22 19:30 ` Khadem Ullah
2025-07-23 11:29 ` Khadem Ullah
2025-07-21 14:50 ` Stephen Hemminger
2025-07-23 14:19 ` Stephen Hemminger
2025-07-29 21:46 ` Stephen Hemminger [this message]
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=20250729144611.46078d65@hermes.local \
--to=stephen@networkplumber.org \
--cc=14pwcse1224@uetpeshawar.edu.pk \
--cc=dev@dpdk.org \
--cc=rasland@nvidia.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).