DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: "Robin Jarry" <rjarry@redhat.com>,
	dev@dpdk.org, "Morten Brørup" <mb@smartsharesystems.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [PATCH dpdk 0/2] IPv6: Fix coverity issues
Date: Wed, 6 Nov 2024 15:48:05 -0500	[thread overview]
Message-ID: <CAJvnSUDc5zP9J=TK77E9fY_DyStFLwu0oEnJrcy85b-kpMMKAg@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8w82+o95_d_sE1+OweeuHjnKfgM2uJdDHRO6yym9vQ6HQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]

Hi,

There isn't a way to pass the patch through to coverity through our
scripting with how we have it written currently. It probably wouldn't be a
big update to start running it based on a given patch provided, if you
think there may be a somewhat regular need for this. I assume in this case
we would not want to push the result to the coverity website, but rather
just print out the result (to be shared on the mailing list or whatnot).

Otherwise, presumably it would be possible for us to manually spin up our
coverity container image, apply the series, and run the coverity check.

I see you have merged this though. I will go ahead and trigger a coverity
run now, just so that you get the results faster. Sorry about the wait here.

On Wed, Nov 6, 2024 at 3:24 PM David Marchand <david.marchand@redhat.com>
wrote:

> On Tue, Nov 5, 2024 at 10:05 PM David Marchand
> <david.marchand@redhat.com> wrote:
> > 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?
>
> Well, let's get those fixes in.
> We will have the answer tomorrow.
>
> Series applied, thanks.
>
>
> --
> David Marchand
>
>

[-- Attachment #2: Type: text/html, Size: 2004 bytes --]

      reply	other threads:[~2024-11-06 20:49 UTC|newest]

Thread overview: 7+ 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 [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='CAJvnSUDc5zP9J=TK77E9fY_DyStFLwu0oEnJrcy85b-kpMMKAg@mail.gmail.com' \
    --to=probb@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=mb@smartsharesystems.com \
    --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).