From: Bruce Richardson <bruce.richardson@intel.com>
To: "Loftus, Ciara" <ciara.loftus@intel.com>
Cc: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Mandal, Anurag" <anurag.mandal@intel.com>
Subject: Re: [PATCH] net/iavf: fix dead store on reset path
Date: Fri, 25 Sep 2026 15:52:22 +0100 [thread overview]
Message-ID: <araKptJ5tfg3jG4V@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <IA4PR11MB927850A9B5619F4035DF06A58E802@IA4PR11MB9278.namprd11.prod.outlook.com>
On Fri, Sep 25, 2026 at 03:33:08PM +0100, Loftus, Ciara wrote:
> > Subject: Re: [PATCH] net/iavf: fix dead store on reset path
> >
> > On 9/25/2026 10:58 AM, Ciara Loftus wrote:
> > > When dev_start fails during reset recovery, the code defers the start
> > > to the next link-up event and resets ret to 0 to avoid treating this
> > > as an error. This is redundant since ret is unconditionally
> > > overwritten by the return value of iavf_post_reset_reconfig()
> > > immediately after. Remove the dead assignment.
> > >
> > > Fixes: 9aac2219dc2a ("net/iavf: defer device start when PF VSI not ready")
> > >
> > > Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> > > ---
> >
> > I wouldn't really qualify this as a bug fix except maybe static analysis
> > tools might flag it so perhaps having a Fixes tag is worth it.
>
> Apologies this was indeed found by static analysis and should have
> included the following tag, if it can be added on apply:
>
> Coverity issue: 506150
>
> >
> > Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
> >
Added the coverity issue tag - because otherwise I was wondering why we
were bothering with this - and applied patch to dpdk-next-net-intel
Thanks,
/Bruce
prev parent reply other threads:[~2026-09-25 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 8:58 [PATCH] net/iavf: fix dead store on reset path Ciara Loftus
2026-09-25 12:04 ` Burakov, Anatoly
2026-09-25 14:33 ` Loftus, Ciara
2026-09-25 14:52 ` Bruce Richardson [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=araKptJ5tfg3jG4V@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=anurag.mandal@intel.com \
--cc=ciara.loftus@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