All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Florian Westphal <fw@strlen.de>
Cc: <netfilter-devel@vger.kernel.org>, sontu21@gmail.com
Subject: Re: [PATCH nf 3/3] selftests: netfilter: add test case for recent mismatch bug
Date: Fri, 4 Apr 2025 13:51:29 +0200	[thread overview]
Message-ID: <20250404135129.3d0b5dc0@elisabeth> (raw)
In-Reply-To: <20250404062105.4285-4-fw@strlen.de>

On Fri,  4 Apr 2025 08:20:54 +0200
Florian Westphal <fw@strlen.de> wrote:

> Without 'nft_set_pipapo: fix incorrect avx2 match of 5th field octet"
> this fails:
> 
> TEST: reported issues
>   Add two elements, flush, re-add       1s                              [ OK ]
>   net,mac with reload                   0s                              [ OK ]
>   net,port,proto                        3s                              [ OK ]
>   avx2 false match                      0s                              [FAIL]
> False match for fe80:dead:01fe:0a02:0b03:6007:8009:a001
> 
> Other tests do not detect the kernel bug as they only alter parts in
> the /64 netmask.
> 
> Signed-off-by: Florian Westphal <fw@strlen.de>

Reviewed-by: Stefano Brivio <sbrivio@redhat.com>

-- 
Stefano


  reply	other threads:[~2025-04-04 11:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04  6:20 [PATCH nf 0/3] nft_set_pipapo: fix incorrect avx2 match of 5th field octet Florian Westphal
2025-04-04  6:20 ` [PATCH nf 1/3] nft_set_pipapo: add avx register usage tracking for NET_DEBUG builds Florian Westphal
2025-04-04 10:40   ` Stefano Brivio
2025-04-04 11:42     ` Florian Westphal
2025-04-04  6:20 ` [PATCH nf 2/3] nft_set_pipapo: fix incorrect avx2 match of 5th field octet Florian Westphal
2025-04-04  8:34   ` Stefano Brivio
2025-04-04  6:20 ` [PATCH nf 3/3] selftests: netfilter: add test case for recent mismatch bug Florian Westphal
2025-04-04 11:51   ` Stefano Brivio [this message]
2025-04-09  9:51     ` sontu mazumdar
2025-04-09 10:13       ` Stefano Brivio

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=20250404135129.3d0b5dc0@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=sontu21@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.