OpenVZ / Virtuozzo kernel development (devel@openvz.org)
 help / color / mirror / Atom feed
From: "Eva Kurchatova (Virtuozzo)" <eva.kurchatova@virtuozzo.com>
To: no-reply@sashiko.virtuozzo.com, khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v2] selftests: forwarding: flush neighbours in the locked port MAB test
Date: Tue, 3 Nov 2026 23:46:02 +0200	[thread overview]
Message-ID: <27978787-b593-4c49-84f5-32537d038147@virtuozzo.com> (raw)
In-Reply-To: <010701a1a27bd6c8-7a2ccfaa-4446-4695-a816-ed2dd68838c3-000000@eu-central-1.amazonses.com>


On 11/3/26 19:36, no-reply@sashiko.virtuozzo.com wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] selftests: commit message has non-upstream Jira URL and Feature: trailer
> --
>
> commit 14e4827eb4828e3a2b673ab078fcd08a723d8929
> Author: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
>
> selftests: forwarding: flush neighbours in the locked port MAB test
>
> This commit adds an "ip neigh flush dev $h1" after the FDB entry is
> replaced in locked_port_mab(). With the flush, the following ping starts
> a fresh neighbour resolution instead of reusing an entry that timed out
> while the port was locked.
>
>> selftests: forwarding: flush neighbours in the locked port MAB test
>>
>> locked_port_mab starts with the neighbour entry for 192.0.2.2 that
>> [ ... ]
>> Fixes: 4a331d346996 ("selftests: forwarding: Add MAC Authentication Bypass (MAB) test cases")
>> https://virtuozzo.atlassian.net/browse/VSTOR-153057
>> Feature: fix selftests
>>
>> Signed-off-by: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
> [Severity: Low]
> This isn't a bug in the code, but the commit message has two lines that
> don't belong in an upstream changelog:
>
> https://virtuozzo.atlassian.net/browse/VSTOR-153057
> Feature: fix selftests
>
> The first line points to a private issue tracker that other readers can't
> open. The second is a "Feature:" trailer, which isn't a recognized kernel
> trailer.
>
> Could both lines be dropped if this patch is sent to mainline or netdev?
>
>> diff --git a/tools/testing/selftests/net/forwarding/bridge_locked_port.sh b/tools/testing/selftests/net/forwarding/bridge_locked_port.sh
>> --- a/tools/testing/selftests/net/forwarding/bridge_locked_port.sh
>> +++ b/tools/testing/selftests/net/forwarding/bridge_locked_port.sh
> [ ... ]
>
>> @@ -201,6 +201,7 @@ locked_port_mab()
>>   	check_err $? "Locked FDB entry not created"
>>   
>>   	bridge fdb replace `mac_get $h1` dev $swp1 master static
>> +	ip neigh flush dev $h1
>>   
>>   	ping_do $h1 192.0.2.2
>>   	check_err $? "Ping did not work after replacing FDB entry"
Indeed so, this is not an upstream mailing list either. The trailers are 
intentional requirement.
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

  reply	other threads:[~2026-11-03 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 17:31 Eva Kurchatova
2026-11-03 17:36 ` no-reply
2026-11-03 21:46   ` Eva Kurchatova (Virtuozzo) [this message]
2026-11-04 20:20 ` Konstantin Khorenko
2026-11-04 20:20 ` Konstantin Khorenko

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=27978787-b593-4c49-84f5-32537d038147@virtuozzo.com \
    --to=eva.kurchatova@virtuozzo.com \
    --cc=devel@openvz.org \
    --cc=khorenko@virtuozzo.com \
    --cc=no-reply@sashiko.virtuozzo.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