DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Sid Ali Cherrati <scherrati1@gmail.com>
Cc: <dev@dpdk.org>, Anatoly Burakov <anatoly.burakov@intel.com>,
	"Vladimir Medvedkin" <vladimir.medvedkin@intel.com>,
	<stable@dpdk.org>
Subject: Re: [PATCH v2 2/2] net/ixgbe: fix return value of close operation
Date: Thu, 23 Jul 2026 11:32:43 +0100	[thread overview]
Message-ID: <amHty43m0CLS63cr@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260715124816.19882-2-scherrati1@gmail.com>

On Wed, Jul 15, 2026 at 02:48:16PM +0200, Sid Ali Cherrati wrote:
> rte_intr_callback_unregister() returns the number of unregistered
> callbacks on success. Since the close operation started returning
> the ret variable instead of 0, this positive value leaks as the
> return value of ixgbe_dev_close(), so applications checking
> rte_eth_dev_close() != 0 treat a successful close as a failure.
> 
> Use a separate cb_ret variable for the unregister return value so a
> successful unregister never clobbers the dev_stop() error already
> stored in ret, and stop retrying once unregister fails with anything
> other than -EAGAIN, since those errors are not transient.
> 
> Fixes: 62024eb82756 ("ethdev: change stop operation callback to return int")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Sid Ali Cherrati <scherrati1@gmail.com>
> ---
> v2: use a temporary cb_ret variable instead of unconditionally zeroing
>     ret, and stop retrying on a non-transient unregister error, so an
>     earlier error is not lost or masked by a successful/failed
>     unregister
> 
>  drivers/net/intel/ixgbe/ixgbe_ethdev.c | 12 ++++++++----
>  1 file changed, 8 insertions(+), 4 deletions(-)
>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
 

  reply	other threads:[~2026-07-23 10:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10 13:46 [PATCH 1/2] net/i40e: fix return value of close operation SidAli CHERRATI
2026-07-10 13:46 ` [PATCH 2/2] net/ixgbe: " SidAli CHERRATI
2026-07-10 15:26   ` Bruce Richardson
2026-07-15 12:48 ` [PATCH v2 1/2] net/i40e: " Sid Ali Cherrati
2026-07-15 12:48   ` [PATCH v2 2/2] net/ixgbe: " Sid Ali Cherrati
2026-07-23 10:32     ` Bruce Richardson [this message]
2026-07-23 10:32   ` [PATCH v2 1/2] net/i40e: " Bruce Richardson
2026-07-23 10:53     ` 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=amHty43m0CLS63cr@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=scherrati1@gmail.com \
    --cc=stable@dpdk.org \
    --cc=vladimir.medvedkin@intel.com \
    /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