From: patchwork-bot+netdevbpf@kernel•org
To: Duoming Zhou <duoming@zju•edu.cn>
Cc: linux-hams@vger•kernel.org, pabeni@redhat•com, jreuter@yaina•de,
ralf@linux-mips•org, davem@davemloft•net, edumazet@google•com,
kuba@kernel•org, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org, thomas@osterried•de
Subject: Re: [PATCH net v5] net: ax25: Fix deadlock caused by skb_recv_datagram in ax25_recvmsg
Date: Wed, 15 Jun 2022 12:20:13 +0000 [thread overview]
Message-ID: <165529561325.20387.9560588021294882995.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220614092557.6713-1-duoming@zju.edu.cn>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft•net>:
On Tue, 14 Jun 2022 17:25:57 +0800 you wrote:
> The skb_recv_datagram() in ax25_recvmsg() will hold lock_sock
> and block until it receives a packet from the remote. If the client
> doesn`t connect to server and calls read() directly, it will not
> receive any packets forever. As a result, the deadlock will happen.
>
> The fail log caused by deadlock is shown below:
>
> [...]
Here is the summary with links:
- [net,v5] net: ax25: Fix deadlock caused by skb_recv_datagram in ax25_recvmsg
https://git.kernel.org/netdev/net/c/219b51a6f040
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-06-15 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 9:25 [PATCH net v5] net: ax25: Fix deadlock caused by skb_recv_datagram in ax25_recvmsg Duoming Zhou
2022-06-14 14:47 ` Eric Dumazet
2022-06-15 12: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=165529561325.20387.9560588021294882995.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=duoming@zju$(echo .)edu.cn \
--cc=edumazet@google$(echo .)com \
--cc=jreuter@yaina$(echo .)de \
--cc=kuba@kernel$(echo .)org \
--cc=linux-hams@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=ralf@linux-mips$(echo .)org \
--cc=thomas@osterried$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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