patches for DPDK stable branches
 help / color / mirror / Atom feed
From: fengchengwen <fengchengwen@huawei.com>
To: Stephen Hemminger <stephen@networkplumber.org>, <dev@dpdk.org>
Cc: <ndabilpuram@marvell.com>, <stable@dpdk.org>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Akhil Goyal <gakhil@marvell.com>,
	Anoob Joseph <anoobj@marvell.com>
Subject: Re: [PATCH v4 3/9] app/test: fix paren typo
Date: Fri, 22 Nov 2024 08:34:36 +0800	[thread overview]
Message-ID: <dbee9d50-48f9-446c-b11a-8fd9db5eda52@huawei.com> (raw)
In-Reply-To: <20241121182443.68025-4-stephen@networkplumber.org>

Acked-by: Chengwen Feng <fengchengwen@huawei.com>

On 2024/11/22 2:23, Stephen Hemminger wrote:
> The parenthesis were in the wrong place so that comparison
> took precedence over assignment in handling IPv6 extension
> headers.  Break up the loop condition to avoid the problem.
> 
> Link: https://pvs-studio.com/en/blog/posts/cpp/1179/
> 
> Fixes: 15ccc647526e ("test/security: test inline reassembly with multi-segment")
> Cc: ndabilpuram@marvell.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
>  app/test/test_security_inline_proto_vectors.h | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/app/test/test_security_inline_proto_vectors.h b/app/test/test_security_inline_proto_vectors.h
> index b3d724bac6..86dfa54777 100644
> --- a/app/test/test_security_inline_proto_vectors.h
> +++ b/app/test/test_security_inline_proto_vectors.h
> @@ -519,10 +519,12 @@ test_vector_payload_populate(struct ip_reassembly_test_packet *pkt,
>  			if (extra_data_sum) {
>  				proto = hdr->proto;
>  				p += sizeof(struct rte_ipv6_hdr);
> -				while (proto != IPPROTO_FRAGMENT &&
> -				       (proto = rte_ipv6_get_next_ext(p, proto, &ext_len) >= 0))
> +				while (proto != IPPROTO_FRAGMENT) {
> +					proto = rte_ipv6_get_next_ext(p, proto, &ext_len);
> +					if (proto < 0)
> +						break;
>  					p += ext_len;
> -
> +				}
>  				/* Found fragment header, update the frag offset */
>  				if (proto == IPPROTO_FRAGMENT) {
>  					frag_ext = (struct rte_ipv6_fragment_ext *)p;


  reply	other threads:[~2024-11-22  0:34 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241114001403.147609-1-stephen@networkplumber.org>
     [not found] ` <20241114192603.41145-1-stephen@networkplumber.org>
2024-11-14 19:24   ` [PATCH v2 01/10] app/test: do not duplicated loop variable Stephen Hemminger
2024-11-15  9:01     ` Bruce Richardson
2024-11-14 19:25   ` [PATCH v2 02/10] app/test: fix typo in address compare Stephen Hemminger
2024-11-14 19:25   ` [PATCH v2 03/10] app/test: fix paren typo Stephen Hemminger
2024-11-15  9:02     ` Bruce Richardson
2024-11-14 19:25   ` [PATCH v2 05/10] app/test: fix TLS zero length record Stephen Hemminger
2024-11-14 19:25   ` [PATCH v2 06/10] app/test: fix operator precedence bug Stephen Hemminger
2024-11-15  9:06     ` Bruce Richardson
2024-11-14 19:25   ` [PATCH v2 07/10] test/eal: fix core check in c flag test Stephen Hemminger
2024-11-15  9:07     ` Bruce Richardson
2024-11-15 19:53       ` Stephen Hemminger
2024-11-14 19:25   ` [PATCH v2 09/10] app/test-pmd: avoid potential outside of array reference Stephen Hemminger
2024-11-15  9:09     ` Bruce Richardson
2024-11-14 19:25   ` [PATCH v2 10/10] app/test-dma-perf: fix parsing of DMA address Stephen Hemminger
2024-11-15  9:13     ` Bruce Richardson
2024-11-15 19:58       ` Stephen Hemminger
     [not found] ` <20241115200751.17141-1-stephen@networkplumber.org>
2024-11-15 20:06   ` [PATCH v3 01/10] app/test: do not duplicate loop variable Stephen Hemminger
2024-11-15 20:06   ` [PATCH v3 02/10] app/test: fix typo in address compare Stephen Hemminger
2024-11-15 20:06   ` [PATCH v3 03/10] app/test: fix paren typo Stephen Hemminger
2024-11-15 20:06   ` [PATCH v3 05/10] app/test: fix TLS zero length record Stephen Hemminger
2024-11-15 20:06   ` [PATCH v3 06/10] app/test: fix operator precedence bug Stephen Hemminger
2024-11-15 20:06   ` [PATCH v3 07/10] test/eal: fix core check in c flag test Stephen Hemminger
2024-11-15 20:06   ` [PATCH v3 09/10] app/test-pmd: avoid potential outside of array reference Stephen Hemminger
2024-11-15 20:06   ` [PATCH v3 10/10] app/test-dma-perf: fix parsing of DMA address Stephen Hemminger
2024-11-18  2:44     ` fengchengwen
     [not found] ` <20241121182443.68025-1-stephen@networkplumber.org>
2024-11-21 18:23   ` [PATCH v4 1/9] app/test: do not duplicate loop variable Stephen Hemminger
2024-11-22  0:39     ` fengchengwen
2024-11-21 18:23   ` [PATCH v4 2/9] app/test: fix typo in address compare Stephen Hemminger
2024-11-22  0:37     ` fengchengwen
2024-11-21 18:23   ` [PATCH v4 3/9] app/test: fix paren typo Stephen Hemminger
2024-11-22  0:34     ` fengchengwen [this message]
2024-11-21 18:23   ` [PATCH v4 5/9] app/test: fix TLS zero length record Stephen Hemminger
2024-11-21 18:23   ` [PATCH v4 6/9] app/test: fix operator precedence bug Stephen Hemminger
2024-11-21 18:23   ` [PATCH v4 7/9] test/eal: fix core check in c flag test Stephen Hemminger
2024-11-21 18:23   ` [PATCH v4 9/9] app/test-pmd: avoid potential outside of array reference Stephen Hemminger
2024-11-22  0:33     ` fengchengwen

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=dbee9d50-48f9-446c-b11a-8fd9db5eda52@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=anoobj@marvell.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).