From: Paolo Abeni <pabeni@redhat.com>
To: Simon Horman <horms@kernel.org>, Danielle Ratson <danieller@nvidia.com>
Cc: netdev@vger.kernel.org, razor@blackwall.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, shuah@kernel.org,
linux-kernel@vger.kernel.org, bridge@lists.linux.dev,
linux-kselftest@vger.kernel.org, idosch@nvidia.com,
petrm@nvidia.com
Subject: Re: [PATCH net 2/2] selftests: net: Add bridge VLAN range grouping tests
Date: Tue, 24 Feb 2026 12:21:09 +0100 [thread overview]
Message-ID: <d3a43f4c-1b6e-4cac-a127-3e297fd6d224@redhat.com> (raw)
In-Reply-To: <aZ1agwUGRt2Qqzv3@horms.kernel.org>
On 2/24/26 9:00 AM, Simon Horman wrote:
> On Sun, Feb 22, 2026 at 10:53:38AM +0200, Danielle Ratson wrote:
>> Add a new test file bridge_vlan_dump.sh with four test cases that verify
>> VLANs with different per-VLAN options are not incorrectly grouped into
>> ranges in the dump output.
>>
>> The tests verify the kernel's br_vlan_opts_eq_range() function correctly
>> prevents VLAN range grouping when neigh_suppress, mcast_max_groups,
>> mcast_n_groups, or mcast_enabled options differ.
>>
>> Each test verifies that VLANs with different option values appear as
>> individual entries rather than ranges, and that VLANs with matching
>> values are properly grouped together.
>>
>> Example output:
>>
>> $ ./bridge_vlan_dump.sh
>> TEST: VLAN range grouping with neigh_suppress [ OK ]
>> TEST: VLAN range grouping with mcast_max_groups [ OK ]
>> TEST: VLAN range grouping with mcast_n_groups [ OK ]
>> TEST: VLAN range grouping with mcast_enabled [ OK ]
>>
>> Signed-off-by: Danielle Ratson <danieller@nvidia.com>
>> Reviewed-by: Petr Machata <petrm@nvidia.com>
>> ---
>> tools/testing/selftests/net/Makefile | 1 +
>> .../testing/selftests/net/bridge_vlan_dump.sh | 203 ++++++++++++++++++
>> 2 files changed, 204 insertions(+)
>> create mode 100755 tools/testing/selftests/net/bridge_vlan_dump.sh
>
> Hi Danielle,
>
> I'm wondering if you could consider running running shellcheck over this
> and cleaning things up a little.
>
> I see SC2086 which I think can be trivially addressed.
> And SC2329, which I think would be best ignored using #shellcheck disable=SC2086
@Danielle: please address the shellcheck-reported issues. We are trying
to avoid them in the new code, and with time we will hopefully achieve
code consistency.
You can use the ingest_mdir.py script from
https://github.com/linux-netdev/nipa/ to automate the shellcheck test
before submission.
Thanks,
Paolo
prev parent reply other threads:[~2026-02-24 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 8:53 [PATCH net 0/2] bridge: Check relevant options in VLAN range grouping Danielle Ratson
2026-02-22 8:53 ` [PATCH net 1/2] bridge: Check relevant per-VLAN " Danielle Ratson
2026-02-22 16:36 ` Nikolay Aleksandrov
2026-02-22 8:53 ` [PATCH net 2/2] selftests: net: Add bridge VLAN range grouping tests Danielle Ratson
2026-02-22 16:36 ` Nikolay Aleksandrov
2026-02-24 8:00 ` Simon Horman
2026-02-24 11:21 ` Paolo Abeni [this message]
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=d3a43f4c-1b6e-4cac-a127-3e297fd6d224@redhat.com \
--to=pabeni@redhat.com \
--cc=bridge@lists.linux.dev \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®