From: patchwork-bot+netdevbpf@kernel.org
To: None <liuyacan@corp.netease.com>
Cc: kgraul@linux.ibm.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ubraun@linux.ibm.com
Subject: Re: [PATCH v2 net] net/smc: postpone sk_refcnt increment in connect()
Date: Mon, 23 May 2022 09:10:22 +0000 [thread overview]
Message-ID: <165329702229.13209.6286752264509182107.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220523045707.1704761-1-liuyacan@corp.netease.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 23 May 2022 12:57:07 +0800 you wrote:
> From: liuyacan <liuyacan@corp.netease.com>
>
> Same trigger condition as commit 86434744. When setsockopt runs
> in parallel to a connect(), and switch the socket into fallback
> mode. Then the sk_refcnt is incremented in smc_connect(), but
> its state stay in SMC_INIT (NOT SMC_ACTIVE). This cause the
> corresponding sk_refcnt decrement in __smc_release() will not be
> performed.
>
> [...]
Here is the summary with links:
- [v2,net] net/smc: postpone sk_refcnt increment in connect()
https://git.kernel.org/netdev/net/c/75c1edf23b95
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-05-23 9:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 3:24 [PATCH net] net/smc: postpone sk_refcnt increment in connect() liuyacan
2022-05-23 4:57 ` [PATCH v2 " liuyacan
2022-05-23 9:10 ` patchwork-bot+netdevbpf [this message]
2022-05-23 12:45 ` Karsten Graul
2022-05-23 14:19 ` liuyacan
2022-05-23 14:44 ` Karsten Graul
2022-05-23 15:21 ` liuyacan
2022-05-24 11:43 ` Tony Lu
2022-05-24 12:11 ` liuyacan
2022-05-24 12:05 ` Karsten Graul
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=165329702229.13209.6286752264509182107.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=liuyacan@corp.netease.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ubraun@linux.ibm.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