From: patchwork-bot+netdevbpf@kernel.org
To: Minxi Hou <houminxi@gmail.com>
Cc: netdev@vger.kernel.org, aconole@redhat.com, davem@davemloft.net,
echaudro@redhat.com, edumazet@google.com, horms@kernel.org,
i.maximets@ovn.org, kuba@kernel.org, pabeni@redhat.com,
shuah@kernel.org, dev@openvswitch.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v4] selftests/net/openvswitch: guard command substitutions against empty output
Date: Tue, 09 Jun 2026 13:20:06 +0000 [thread overview]
Message-ID: <178101120615.2025134.17400866656842960591.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260604163016.3929371-1-houminxi@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 5 Jun 2026 00:30:16 +0800 you wrote:
> When ip-link output is unavailable, when the upcall daemon log has not
> been written yet, or when pahole does not know the OVS drop subsystem
> ID, the affected command substitutions silently produce empty strings.
> The caller then passes empty sha= or pid= arguments to ovs_add_flow,
> or matches against wrong drop reason codes, all without a diagnostic.
>
> Add [ -z ] guards immediately after each assignment. For test_arp_ping,
> also align the MAC extraction to use awk '/link\/ether/' as in
> test_pop_vlan. The drop_reason guard returns ksft_skip because an
> absent subsystem ID is an environment issue, not a test failure.
>
> [...]
Here is the summary with links:
- [net,v4] selftests/net/openvswitch: guard command substitutions against empty output
https://git.kernel.org/netdev/net-next/c/9415471e01c1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-09 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 16:30 [PATCH net v4] selftests/net/openvswitch: guard command substitutions against empty output Minxi Hou
2026-06-09 10:58 ` Paolo Abeni
2026-06-09 11:18 ` Eelco Chaudron
2026-06-09 12:57 ` Aaron Conole
2026-06-09 13:20 ` patchwork-bot+netdevbpf [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=178101120615.2025134.17400866656842960591.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=houminxi@gmail.com \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox