From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 28BCD45C9E; Wed, 6 Nov 2024 21:49:57 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B845F42EB5; Wed, 6 Nov 2024 21:49:56 +0100 (CET) Received: from mail-pg1-f179.google.com (mail-pg1-f179.google.com [209.85.215.179]) by mails.dpdk.org (Postfix) with ESMTP id CC66042EA7 for ; Wed, 6 Nov 2024 21:49:54 +0100 (CET) Received: by mail-pg1-f179.google.com with SMTP id 41be03b00d2f7-7ea9739647bso241281a12.0 for ; Wed, 06 Nov 2024 12:49:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1730926194; x=1731530994; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=b2jCmrCd7St+Fjj1sv5A7pSaugs+gJpgMZp461Jr9OE=; b=GkmVhB2Z+a+bf1/gvZ1BsINN+HMcNzP7mHG8ji3B0pBA835VIaMcmLhJULBfd4vsBA I/KBWg+3paM9vOhXoHnWpGoCsNsJznMm4KkQGXLALDmtoaCycKiTVldjz3cIW058WMBW hsDJ25vMUd26gH4VRgsIpIIcILnoZy2sZoEnI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730926194; x=1731530994; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=b2jCmrCd7St+Fjj1sv5A7pSaugs+gJpgMZp461Jr9OE=; b=gowLgtcaW+FFn87BWrUt/4mKRItM9xLV0AkcnB/PaXMpQu/qWboUB2y2pIFQCbRark W3arq/cDxgFjyIu7RjeRbD0LXftk+tsDdfN4Y1372M39l/Ng80cbV6qIzgyXxM0eKPNZ YDCvj43SdmteP9saWmrM7rCO2Pn6iPyKDz+2uyJ08K3H005ULCPvacp8TCPJcuALrbLH /TJLdzcmDUSi2wxW4hNrLrRnkzlXpcN0zs1TLWaiy4A3QgG6Ci9aE1hIR308g7v4pugL 5DLrD/EMMMrmzt8mVoycnsbbsozw61uyeYXxM356Vk8bl1vH0z2k6KIovSVuew2rUXd+ WSBA== X-Forwarded-Encrypted: i=1; AJvYcCW0R7QPrOEfHMfmkIXneOdEwbti1PkfHdSW0oOMoSnLponH4HqcZmX3jnmdyw9tLhb/X4A=@dpdk.org X-Gm-Message-State: AOJu0YwVUYBQD+4iIR4O55RRoXrZFFf8SqYdu7ugeKettQO9Lc3ufmHa rx7Bl99fJhoBDGbO62uU1xqLaquZcq2JZP6YWPvuJKtAVDRSKbcHBImq+3kApfgWzH5O8qQMnkJ KD+hQUXZpFu25NxullpPncMCbMMWa4QrbQDL+hA== X-Google-Smtp-Source: AGHT+IFTwVDrNNjE113wpy2ddIFFKbSoexEP3GaLLWd6mxfECELo4LkVofP5Cwg/KffN3vXhefsmo/6ukK+SPPQhn6c= X-Received: by 2002:a17:90b:1c10:b0:2e2:cef9:8f68 with SMTP id 98e67ed59e1d1-2e8f1059571mr45294714a91.4.1730926193836; Wed, 06 Nov 2024 12:49:53 -0800 (PST) MIME-Version: 1.0 References: <20241024151919.400878-4-rjarry@redhat.com> In-Reply-To: From: Patrick Robb Date: Wed, 6 Nov 2024 15:48:05 -0500 Message-ID: Subject: Re: [PATCH dpdk 0/2] IPv6: Fix coverity issues To: David Marchand Cc: Robin Jarry , dev@dpdk.org, =?UTF-8?Q?Morten_Br=C3=B8rup?= , "Mcnamara, John" Content-Type: multipart/alternative; boundary="000000000000eaa412062644a879" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --000000000000eaa412062644a879 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=E2=80=AFPM David Marchand wrote: > On Tue, Nov 5, 2024 at 10:05=E2=80=AFPM David Marchand > wrote: > > On Thu, Oct 24, 2024 at 5:20=E2=80=AFPM Robin Jarry = 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 > > --000000000000eaa412062644a879 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

There isn't a way to pass the p= atch 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 bas= ed 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 t= o the coverity website, but rather just print out the result (to be shared = on the mailing list or whatnot).

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

<= div>I see you have merged this though. I will go ahead and trigger a coveri= ty run now, just so that you get the=C2=A0results faster. Sorry about the w= ait here.

On Wed, Nov 6, 2024 at 3:24=E2=80=AFPM David Marchand <<= a href=3D"mailto:david.marchand@redhat.com">david.marchand@redhat.com&g= t; wrote:
On Tue= , Nov 5, 2024 at 10:05=E2=80=AFPM David Marchand
<david.ma= rchand@redhat.com> wrote:
> On Thu, Oct 24, 2024 at 5:20=E2=80=AFPM 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

--000000000000eaa412062644a879--