From: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>, <dev@dpdk.org>
Subject: Re: [PATCH v2 4/4] net/ixgbe: prevent crashes in secondary processes
Date: Mon, 17 Feb 2025 17:28:01 +0000 [thread overview]
Message-ID: <5465b94b-e415-453f-a826-a4ef5b445252@intel.com> (raw)
In-Reply-To: <11dadf1bf66aa2129a08b588b68ec0a8c992cfaa.1739800426.git.anatoly.burakov@intel.com>
Acked-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
On 17/02/2025 13:54, Anatoly Burakov wrote:
> Currently, the architecture of IXGBE base driver is such that it uses
> function pointers internally. These are not guaranteed to be valid in
> secondary processes, which can lead to crashes. This patch prevents IXGBE
> ethdev driver from calling into these functions.
>
> Bugzilla ID: 1575
>
> Fixes: af75078fece3 ("first public release")
> Cc: stable@dpdk.org
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
> doc/guides/nics/ixgbe.rst | 14 ++
> drivers/net/intel/ixgbe/ixgbe_ethdev.c | 242 +++++++++++++++++++++++++
> 2 files changed, 256 insertions(+)
>
<snip>
--
Regards,
Vladimir
next prev parent reply other threads:[~2025-02-17 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 16:19 [PATCH v1 1/4] net/e1000: " Anatoly Burakov
2024-12-12 16:19 ` [PATCH v1 2/4] net/igb: " Anatoly Burakov
2024-12-12 16:19 ` [PATCH v1 3/4] net/igc: " Anatoly Burakov
2024-12-12 16:19 ` [PATCH v1 4/4] net/ixgbe: " Anatoly Burakov
2024-12-12 18:02 ` [PATCH v1 1/4] net/e1000: " Stephen Hemminger
2024-12-13 9:09 ` Burakov, Anatoly
2025-02-17 13:54 ` [PATCH v2 " Anatoly Burakov
2025-02-17 13:54 ` [PATCH v2 2/4] " Anatoly Burakov
2025-02-17 13:54 ` [PATCH v2 3/4] " Anatoly Burakov
2025-02-17 13:54 ` [PATCH v2 4/4] net/ixgbe: " Anatoly Burakov
2025-02-17 17:28 ` Medvedkin, Vladimir [this message]
2025-02-17 15:28 ` [PATCH v2 1/4] net/e1000: " Bruce Richardson
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=5465b94b-e415-453f-a826-a4ef5b445252@intel.com \
--to=vladimir.medvedkin@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@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).