From: patchwork-bot+netdevbpf@kernel.org
To: Baowen Zheng <baowen.zheng@corigine.com>
Cc: davem@davemloft.net, kuba@kernel.org, xiyou.wangcong@gmail.com,
jhs@mojatatu.com, jiri@resnulli.us, netdev@vger.kernel.org,
louis.peens@corigine.com, oss-drivers@corigine.com,
eric.dumazet@gmail.com, simon.horman@corigine.com
Subject: Re: [PATCH net-next v1] flow_offload: fix suspicious RCU usage when offloading tc action
Date: Thu, 23 Dec 2021 11:20:09 +0000 [thread overview]
Message-ID: <164025840984.28761.7314510545220370003.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1640147146-4294-1-git-send-email-baowen.zheng@corigine.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 22 Dec 2021 12:25:46 +0800 you wrote:
> Fix suspicious rcu_dereference_protected() usage when offloading tc action.
>
> We should hold tcfa_lock to offload tc action in action initiation.
>
> Without these changes, the following warning will be observed:
>
> WARNING: suspicious RCU usage
> 5.16.0-rc5-net-next-01504-g7d1f236dcffa-dirty #50 Tainted: G I
>
> [...]
Here is the summary with links:
- [net-next,v1] flow_offload: fix suspicious RCU usage when offloading tc action
https://git.kernel.org/netdev/net-next/c/963178a06352
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-12-23 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 4:25 [PATCH net-next v1] flow_offload: fix suspicious RCU usage when offloading tc action Baowen Zheng
2021-12-23 11: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=164025840984.28761.7314510545220370003.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=baowen.zheng@corigine.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=simon.horman@corigine.com \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).