From: patchwork-bot+netdevbpf@kernel.org
To: zhangzhengming <zhangzhengming@huawei.com>
Cc: roopa@nvidia.com, nikolay@nvidia.com, davem@davemloft.net,
kuba@kernel.org, bridge@lists.linux-foundation.org,
netdev@vger.kernel.org, wangxiaogang3@huawei.com,
xuhanbing@huawei.com
Subject: Re: [PATCH v2] bridge: Fix possible races between assigning rx_handler_data and setting IFF_BRIDGE_PORT bit
Date: Thu, 29 Apr 2021 22:40:10 +0000 [thread overview]
Message-ID: <161973601038.15907.11344410460500659654.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1619620694-12419-1-git-send-email-zhangzhengming@huawei.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Wed, 28 Apr 2021 22:38:14 +0800 you wrote:
> From: Zhang Zhengming <zhangzhengming@huawei.com>
>
> There is a crash in the function br_get_link_af_size_filtered,
> as the port_exists(dev) is true and the rx_handler_data of dev is NULL.
> But the rx_handler_data of dev is correct saved in vmcore.
>
> The oops looks something like:
> ...
> pc : br_get_link_af_size_filtered+0x28/0x1c8 [bridge]
> ...
> Call trace:
> br_get_link_af_size_filtered+0x28/0x1c8 [bridge]
> if_nlmsg_size+0x180/0x1b0
> rtnl_calcit.isra.12+0xf8/0x148
> rtnetlink_rcv_msg+0x334/0x370
> netlink_rcv_skb+0x64/0x130
> rtnetlink_rcv+0x28/0x38
> netlink_unicast+0x1f0/0x250
> netlink_sendmsg+0x310/0x378
> sock_sendmsg+0x4c/0x70
> __sys_sendto+0x120/0x150
> __arm64_sys_sendto+0x30/0x40
> el0_svc_common+0x78/0x130
> el0_svc_handler+0x38/0x78
> el0_svc+0x8/0xc
>
> [...]
Here is the summary with links:
- [v2] bridge: Fix possible races between assigning rx_handler_data and setting IFF_BRIDGE_PORT bit
https://git.kernel.org/netdev/net/c/59259ff7a81b
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-04-29 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 14:38 [PATCH v2] bridge: Fix possible races between assigning rx_handler_data and setting IFF_BRIDGE_PORT bit zhangzhengming
2021-04-29 22:40 ` 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=161973601038.15907.11344410460500659654.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=roopa@nvidia.com \
--cc=wangxiaogang3@huawei.com \
--cc=xuhanbing@huawei.com \
--cc=zhangzhengming@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 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).