From: patchwork-bot+netdevbpf@kernel.org
To: Tung Nguyen <tung.q.nguyen@dektech.com.au>
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
davem@davemloft.net, kuba@kernel.org, shuali@redhat.com,
jmaloy@redhat.com
Subject: Re: [PATCH net v2 1/1] tipc: fix kernel panic when enabling bearer
Date: Fri, 04 Mar 2022 13:20:10 +0000 [thread overview]
Message-ID: <164640001008.11229.394495890772849018.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220304032518.9305-1-tung.q.nguyen@dektech.com.au>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 4 Mar 2022 03:25:18 +0000 you wrote:
> When enabling a bearer on a node, a kernel panic is observed:
>
> [ 4.498085] RIP: 0010:tipc_mon_prep+0x4e/0x130 [tipc]
> ...
> [ 4.520030] Call Trace:
> [ 4.520689] <IRQ>
> [ 4.521236] tipc_link_build_proto_msg+0x375/0x750 [tipc]
> [ 4.522654] tipc_link_build_state_msg+0x48/0xc0 [tipc]
> [ 4.524034] __tipc_node_link_up+0xd7/0x290 [tipc]
> [ 4.525292] tipc_rcv+0x5da/0x730 [tipc]
> [ 4.526346] ? __netif_receive_skb_core+0xb7/0xfc0
> [ 4.527601] tipc_l2_rcv_msg+0x5e/0x90 [tipc]
> [ 4.528737] __netif_receive_skb_list_core+0x20b/0x260
> [ 4.530068] netif_receive_skb_list_internal+0x1bf/0x2e0
> [ 4.531450] ? dev_gro_receive+0x4c2/0x680
> [ 4.532512] napi_complete_done+0x6f/0x180
> [ 4.533570] virtnet_poll+0x29c/0x42e [virtio_net]
> ...
>
> [...]
Here is the summary with links:
- [net,v2,1/1] tipc: fix kernel panic when enabling bearer
https://git.kernel.org/netdev/net/c/be4977b847f5
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:[~2022-03-04 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 3:25 [PATCH net v2 1/1] tipc: fix kernel panic when enabling bearer Tung Nguyen
2022-03-04 13: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=164640001008.11229.394495890772849018.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuali@redhat.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tung.q.nguyen@dektech.com.au \
/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.