From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>, <dev@dpdk.org>
Cc: <stable@dpdk.org>
Subject: Re: [PATCH] net/i40e: fix missing error handling for QinQ filter
Date: Fri, 11 Sep 2026 13:16:57 +0200 [thread overview]
Message-ID: <d2b9b9da-f238-4207-8f4f-4476afe98014@intel.com> (raw)
In-Reply-To: <20260911094043.1683329-1-bruce.richardson@intel.com>
On 9/11/2026 11:40 AM, Bruce Richardson wrote:
> When installing a QinQ tunnel filter, errors were not properly caught
> leading to the situation where the app got a successful return code even
> though the filter was not properly installed. Add an appropriate log
> message and error return code on error to fix.
>
> Fixes: 116b7910d641 ("net/i40e: add QinQ filter create function")
> Cc: stable@dpdk.org
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> drivers/net/intel/i40e/i40e_ethdev.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/intel/i40e/i40e_ethdev.c b/drivers/net/intel/i40e/i40e_ethdev.c
> index b6b2d291ee..c91abe7626 100644
> --- a/drivers/net/intel/i40e/i40e_ethdev.c
> +++ b/drivers/net/intel/i40e/i40e_ethdev.c
> @@ -8597,9 +8597,11 @@ i40e_dev_consistent_tunnel_filter_set(struct i40e_pf *pf,
> case I40E_TUNNEL_TYPE_QINQ:
> if (!pf->qinq_replace_flag) {
> ret = i40e_cloud_filter_qinq_create(pf);
> - if (ret < 0)
> - PMD_DRV_LOG(DEBUG,
> - "QinQ tunnel filter already created.");
> + if (ret < 0) {
> + PMD_DRV_LOG(ERR, "Failed to create QinQ tunnel filter.");
> + /* ret is a raw i40e_status_code, not an errno */
> + return -ENOTSUP;
> + }
> pf->qinq_replace_flag = 1;
> }
> /* Add in the General fields the values of
Returning ENOTSUP unconditionally seemed unwarranted to me, so I dug
into the code to see what sort of errors we might see. The function in
question actually mixes return values (default value is `-ENOTSUP` which
is -95, but most errors from that codepath return `I40E_NOT_SUPPORTED`
which is -64), but most of them indeed boil down to ENOTSUP (except for
status returned from call into AQ command).
So, although not ideal, this is probably consistent with current
implementation
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2026-09-11 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 9:40 [PATCH] net/i40e: fix missing error handling for QinQ filter Bruce Richardson
2026-09-11 11:16 ` Burakov, Anatoly [this message]
2026-09-11 14:32 ` 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=d2b9b9da-f238-4207-8f4f-4476afe98014@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--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