From: patchwork-bot+netdevbpf@kernel.org
To: Paolo Pisati <paolo.pisati@canonical.com>
Cc: davem@davemloft.net, kuba@kernel.org, shuah@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: net: devlink_port_split: check devlink returned an element before dereferencing it
Date: Mon, 28 Jun 2021 23:20:03 +0000 [thread overview]
Message-ID: <162492240312.3183.18165138324418989489.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210628145424.69146-1-paolo.pisati@canonical.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Mon, 28 Jun 2021 16:54:24 +0200 you wrote:
> And thus avoid a Python stacktrace:
>
> ~/linux/tools/testing/selftests/net$ ./devlink_port_split.py
> Traceback (most recent call last):
> File "/home/linux/tools/testing/selftests/net/./devlink_port_split.py",
> line 277, in <module> main()
> File "/home/linux/tools/testing/selftests/net/./devlink_port_split.py",
> line 242, in main
> dev = list(devs.keys())[0]
> IndexError: list index out of range
>
> [...]
Here is the summary with links:
- selftests: net: devlink_port_split: check devlink returned an element before dereferencing it
https://git.kernel.org/netdev/net/c/a118ff661889
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:[~2021-06-28 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 14:54 [PATCH] selftests: net: devlink_port_split: check devlink returned an element before dereferencing it Paolo Pisati
2021-06-28 23: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=162492240312.3183.18165138324418989489.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paolo.pisati@canonical.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;
as well as URLs for NNTP newsgroup(s).