From: patchwork-bot+netdevbpf@kernel.org
To: zhudi <zhudi21@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
rose.chen@huawei.com
Subject: Re: [PATCH] pktgen: fix misuse of BUG_ON() in pktgen_thread_worker()
Date: Thu, 28 Jan 2021 00:50:10 +0000 [thread overview]
Message-ID: <161179501091.14572.11655971573513336606.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210125124229.19334-1-zhudi21@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 25 Jan 2021 20:42:29 +0800 you wrote:
> From: Di Zhu <zhudi21@huawei.com>
>
> pktgen create threads for all online cpus and bond these threads to
> relevant cpu repecivtily. when this thread firstly be woken up, it
> will compare cpu currently running with the cpu specified at the time
> of creation and if the two cpus are not equal, BUG_ON() will take effect
> causing panic on the system.
> Notice that these threads could be migrated to other cpus before start
> running because of the cpu hotplug after these threads have created. so the
> BUG_ON() used here seems unreasonable and we can replace it with WARN_ON()
> to just printf a warning other than panic the system.
>
> [...]
Here is the summary with links:
- pktgen: fix misuse of BUG_ON() in pktgen_thread_worker()
https://git.kernel.org/netdev/net-next/c/275b1e88cabb
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-01-28 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 12:42 [PATCH] pktgen: fix misuse of BUG_ON() in pktgen_thread_worker() zhudi
2021-01-28 0:50 ` 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=161179501091.14572.11655971573513336606.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rose.chen@huawei.com \
--cc=zhudi21@huawei.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 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.