From: Guillaume Nault <gnault@redhat.com>
To: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: POSSIBLE BUG: selftests/net/fcnal-test.sh: [FAIL][FIX TESTED] in vrf "bind - ns-B IPv6 LLA" test
Date: Wed, 7 Jun 2023 18:51:59 +0200 [thread overview]
Message-ID: <ZIC1r6IHOM5nr9QD@debian> (raw)
In-Reply-To: <a3b2891d-d355-dacd-24ec-af9f8aacac57@alu.unizg.hr>
On Wed, Jun 07, 2023 at 12:04:52AM +0200, Mirsad Goran Todorovac wrote:
> I cannot tell if those are new for the architecture (Ubuntu 22.04 + AMD Ryzen)
>
> However, Ubuntu's unsigned 6.3.1 generic mainline kernel is also affected.
> So, it might seem like an old problem.
>
> (If you could isolate the exact tests, I could try a bisect.)
>
> [...]
> TEST: ping local, VRF bind - ns-A IP [ OK ]
> TEST: ping local, VRF bind - VRF IP [FAIL]
> TEST: ping local, VRF bind - loopback [ OK ]
> TEST: ping local, device bind - ns-A IP [FAIL]
> TEST: ping local, device bind - VRF IP [ OK ]
> [...]
>
> SYSCTL: net.ipv4.raw_l3mdev_accept=1
>
> [...]
> TEST: ping local, VRF bind - ns-A IP [ OK ]
> TEST: ping local, VRF bind - VRF IP [FAIL]
> TEST: ping local, VRF bind - loopback [ OK ]
> TEST: ping local, device bind - ns-A IP [FAIL]
> TEST: ping local, device bind - VRF IP [ OK ]
> [...]
>
> Yes, just tested, w commit 42510dffd0e2 these are still present
> in fcnal-test.sh output:
>
> [...]
> TEST: ping local, VRF bind - ns-A IP [ OK ]
> TEST: ping local, VRF bind - VRF IP [FAIL]
> TEST: ping local, VRF bind - loopback [ OK ]
> TEST: ping local, device bind - ns-A IP [FAIL]
> TEST: ping local, device bind - VRF IP [ OK ]
> [...]
> TEST: ping local, VRF bind - ns-A IP [ OK ]
> TEST: ping local, VRF bind - VRF IP [FAIL]
> TEST: ping local, VRF bind - loopback [ OK ]
> TEST: ping local, device bind - ns-A IP [FAIL]
> TEST: ping local, device bind - VRF IP [ OK ]
> [...]
I have the same failures here. They don't seem to be recent.
I'll take a look.
> I have attached the config used and lshw.
>
> Best regards,
> Mirsad
next prev parent reply other threads:[~2023-06-07 16:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 12:17 POSSIBLE BUG: selftests/net/fcnal-test.sh: [FAIL] in vrf "bind - ns-B IPv6 LLA" test Mirsad Todorovac
2023-05-31 18:11 ` Guillaume Nault
2023-06-02 12:35 ` Mirsad Goran Todorovac
2023-06-06 6:24 ` Mirsad Goran Todorovac
2023-06-06 13:46 ` Guillaume Nault
2023-06-06 13:57 ` Mirsad Todorovac
2023-06-06 14:11 ` Guillaume Nault
2023-06-06 14:28 ` Mirsad Todorovac
2023-06-06 18:50 ` Guillaume Nault
2023-06-06 19:17 ` Mirsad Goran Todorovac
2023-06-06 19:27 ` Guillaume Nault
2023-06-06 18:07 ` POSSIBLE BUG: selftests/net/fcnal-test.sh: [FAIL][FIX TESTED] " Mirsad Goran Todorovac
2023-06-06 18:57 ` Guillaume Nault
2023-06-06 22:04 ` Mirsad Goran Todorovac
2023-06-07 16:51 ` Guillaume Nault [this message]
2023-06-08 5:37 ` Mirsad Goran Todorovac
2023-06-09 16:13 ` Guillaume Nault
2023-06-10 18:04 ` Mirsad Goran Todorovac
2023-06-14 8:47 ` Guillaume Nault
2023-06-15 20:10 ` Mirsad Goran Todorovac
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=ZIC1r6IHOM5nr9QD@debian \
--to=gnault@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.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 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.