From: patchwork-bot+netdevbpf@kernel.org
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, cong.wang@bytedance.com,
syzbot+82752bc5331601cf4899@syzkaller.appspotmail.com,
syzbot+b3b63b6bff456bd95294@syzkaller.appspotmail.com,
syzbot+ba67b12b1ca729912834@syzkaller.appspotmail.com,
jhs@mojatatu.com, jiri@resnulli.us
Subject: Re: [Patch net-next] net_sched: fix RTNL deadlock again caused by request_module()
Date: Tue, 19 Jan 2021 04:30:09 +0000 [thread overview]
Message-ID: <161103060914.4335.6975760467315017794.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210117005657.14810-1-xiyou.wangcong@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Sat, 16 Jan 2021 16:56:57 -0800 you wrote:
> From: Cong Wang <cong.wang@bytedance.com>
>
> tcf_action_init_1() loads tc action modules automatically with
> request_module() after parsing the tc action names, and it drops RTNL
> lock and re-holds it before and after request_module(). This causes a
> lot of troubles, as discovered by syzbot, because we can be in the
> middle of batch initializations when we create an array of tc actions.
>
> [...]
Here is the summary with links:
- [net-next] net_sched: fix RTNL deadlock again caused by request_module()
https://git.kernel.org/netdev/net-next/c/d349f9976868
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-19 4:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 0:56 [Patch net-next] net_sched: fix RTNL deadlock again caused by request_module() Cong Wang
2021-01-17 15:15 ` Jamal Hadi Salim
2021-01-18 14:31 ` Vlad Buslov
2021-01-19 4:30 ` 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=161103060914.4335.6975760467315017794.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cong.wang@bytedance.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=syzbot+82752bc5331601cf4899@syzkaller.appspotmail.com \
--cc=syzbot+b3b63b6bff456bd95294@syzkaller.appspotmail.com \
--cc=syzbot+ba67b12b1ca729912834@syzkaller.appspotmail.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 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.