From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Marchand, David" <david.marchand@redhat.com>,
Patrick Robb <probb@iol.unh.edu>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Robin Jarry" <rjarry@redhat.com>,
"Morten Brørup" <mb@smartsharesystems.com>
Subject: RE: [PATCH dpdk 0/2] IPv6: Fix coverity issues
Date: Sun, 24 Nov 2024 18:58:48 +0000 [thread overview]
Message-ID: <PH8PR11MB6804D7A448EEFBE9D049F2E8FC2D2@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8wC=q5tzDW7sTXHJM9MjzWoQjBxknTpAO24fxHCkiGP5w@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Tuesday, November 5, 2024 9:06 PM
> To: Mcnamara, John <john.mcnamara@intel.com>; Patrick Robb
> <probb@iol.unh.edu>
> Cc: dev@dpdk.org; Robin Jarry <rjarry@redhat.com>; Morten Brørup
> <mb@smartsharesystems.com>
> Subject: Re: [PATCH dpdk 0/2] IPv6: Fix coverity issues
>
> Hello John, Patrick,
>
> On Thu, Oct 24, 2024 at 5:20 PM Robin Jarry <rjarry@redhat.com> wrote:
> >
> > Here are fixes for three coverity issues:
>
> This series fixes two coverity issues. The fixes look correct.
> But the Coverity reports are not obvious to me.
>
> Is there a way to pass those fixes through Coverity to confirm the two
> issues are indeed fixed?
There is no easy way to do that. The Coverity analysis only runs on the main after patches have been merged. It isn't structured to allow patch or fix based analysis.
prev parent reply other threads:[~2024-11-24 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 15:19 Robin Jarry
2024-10-24 15:19 ` [PATCH dpdk 1/2] net/ipv6: fix overflowed array index reads Robin Jarry
2024-10-24 15:19 ` [PATCH dpdk 2/2] net/ipv6: fix out-of-bounds read Robin Jarry
2024-10-24 15:37 ` [PATCH dpdk 0/2] IPv6: Fix coverity issues Morten Brørup
2024-11-05 21:05 ` David Marchand
2024-11-06 20:24 ` David Marchand
2024-11-06 20:48 ` Patrick Robb
2024-11-24 18:58 ` Mcnamara, John [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=PH8PR11MB6804D7A448EEFBE9D049F2E8FC2D2@PH8PR11MB6804.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=probb@iol.unh.edu \
--cc=rjarry@redhat.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;
as well as URLs for NNTP newsgroup(s).