From: Bruce Richardson <bruce.richardson@intel.com>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v1 1/4] net/ice: fix potential NULL dereference
Date: Fri, 26 Jun 2026 10:08:49 +0100 [thread overview]
Message-ID: <aj5BoQp_vcSGyIx8@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <aj48r5GCYmLvhZ5X@bricha3-mobl1.ger.corp.intel.com>
On Fri, Jun 26, 2026 at 09:47:43AM +0100, Bruce Richardson wrote:
> On Thu, Jun 25, 2026 at 04:48:10PM +0100, Anatoly Burakov wrote:
> > Static analysis reports that a rule might have a valid engine but invalid
> > rule pointer while having a valid rule size. This should not happen in
> > normal operation, but it's a good defensive check, so fix the potential
> > issue by checking for the problematic condition before dumping flow memory.
> >
> > Coverity issue: 503774
> >
> > Fixes: 215a768c180a ("net/ice: support flow dump")
> >
> > Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> > ---
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Series applied to dpdk-next-net-intel.
Thanks,
/Bruce
prev parent reply other threads:[~2026-06-26 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 15:48 [PATCH v1 1/4] net/ice: fix potential NULL dereference Anatoly Burakov
2026-06-25 15:48 ` [PATCH v1 2/4] net/ixgbe: " Anatoly Burakov
2026-06-26 8:48 ` Bruce Richardson
2026-06-25 15:48 ` [PATCH v1 3/4] net/i40e: " Anatoly Burakov
2026-06-26 8:48 ` Bruce Richardson
2026-06-25 15:48 ` [PATCH v1 4/4] net/iavf: " Anatoly Burakov
2026-06-26 8:49 ` Bruce Richardson
2026-06-26 8:47 ` [PATCH v1 1/4] net/ice: " Bruce Richardson
2026-06-26 9:08 ` 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=aj5BoQp_vcSGyIx8@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@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