From: patchwork-bot+netdevbpf@kernel.org
To: D. Wythe <alibuda@linux.alibaba.com>
Cc: kgraul@linux.ibm.com, wenjia@linux.ibm.com, jaka@linux.ibm.com,
wintera@linux.ibm.com, kuba@kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, linux-s390@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net v2 0/3] bugfixs for smc
Date: Mon, 06 Nov 2023 10:10:24 +0000 [thread overview]
Message-ID: <169926542449.26451.2583545485943327625.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1698991660-82957-1-git-send-email-alibuda@linux.alibaba.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 3 Nov 2023 14:07:37 +0800 you wrote:
> From: "D. Wythe" <alibuda@linux.alibaba.com>
>
> This patches includes bugfix following:
>
> 1. hung state
> 2. sock leak
> 3. potential panic
>
> [...]
Here is the summary with links:
- [net,v2,1/3] net/smc: fix dangling sock under state SMC_APPFINCLOSEWAIT
https://git.kernel.org/netdev/net/c/5211c9729484
- [net,v2,2/3] net/smc: allow cdc msg send rather than drop it with NULL sndbuf_desc
https://git.kernel.org/netdev/net/c/c5bf605ba4f9
- [net,v2,3/3] net/smc: put sk reference if close work was canceled
https://git.kernel.org/netdev/net/c/aa96fbd6d78d
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:[~2023-11-06 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 6:07 [PATCH net v2 0/3] bugfixs for smc D. Wythe
2023-11-03 6:07 ` [PATCH net v2 1/3] net/smc: fix dangling sock under state SMC_APPFINCLOSEWAIT D. Wythe
2023-11-03 6:07 ` [PATCH net v2 2/3] net/smc: allow cdc msg send rather than drop it with NULL sndbuf_desc D. Wythe
2023-11-03 6:07 ` [PATCH net v2 3/3] net/smc: put sk reference if close work was canceled D. Wythe
2023-11-03 8:13 ` [PATCH net v2 0/3] bugfixs for smc Wenjia Zhang
2023-11-06 10:10 ` 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=169926542449.26451.2583545485943327625.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=jaka@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wenjia@linux.ibm.com \
--cc=wintera@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 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.