From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Kevin Traynor <ktraynor@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Maayan Kashani <mkashani@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>, Ori Kam <orika@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] net/mlx5: fix flow null ops seg fault
Date: Tue, 18 Feb 2025 11:04:24 +0000 [thread overview]
Message-ID: <CH3PR12MB84601412137591E85FC64022A4FA2@CH3PR12MB8460.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20250214100545.413991-1-ktraynor@redhat.com>
> -----Original Message-----
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: Friday, February 14, 2025 11:06
> To: dev@dpdk.org
> Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>; Maayan Kashani
> <mkashani@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>; Ori Kam
> <orika@nvidia.com>; Kevin Traynor <ktraynor@redhat.com>; stable@dpdk.org
> Subject: [PATCH] net/mlx5: fix flow null ops seg fault
>
> External email: Use caution opening links or attachments
>
>
> flow null driver ops may get selected and try to call .list_create causing a seg fault.
>
> Full details and back traces in bugzilla.
>
> Add a null ops implementation for .list_create.
>
> Bugzilla ID: 1661
> Fixes: e38776c36c8a ("net/mlx5: introduce HWS for non-template flow API")
> Cc: stable@dpdk.org
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
For segfault fix:
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Regarding why null ops where selected here, let's continue on Bugzilla.
Best regards,
Dariusz Sosnowski
prev parent reply other threads:[~2025-02-18 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 10:05 Kevin Traynor
2025-02-18 11:04 ` Dariusz Sosnowski [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=CH3PR12MB84601412137591E85FC64022A4FA2@CH3PR12MB8460.namprd12.prod.outlook.com \
--to=dsosnowski@nvidia.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=mkashani@nvidia.com \
--cc=orika@nvidia.com \
--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).