From: David Marchand <david.marchand@redhat.com>
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
Date: Tue, 5 Nov 2024 22:05:39 +0100 [thread overview]
Message-ID: <CAJFAV8wC=q5tzDW7sTXHJM9MjzWoQjBxknTpAO24fxHCkiGP5w@mail.gmail.com> (raw)
In-Reply-To: <20241024151919.400878-4-rjarry@redhat.com>
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?
--
David Marchand
next prev parent reply other threads:[~2024-11-05 21:05 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 [this message]
2024-11-06 20:24 ` David Marchand
2024-11-06 20:48 ` Patrick Robb
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='CAJFAV8wC=q5tzDW7sTXHJM9MjzWoQjBxknTpAO24fxHCkiGP5w@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--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).