From: patchwork-bot+netdevbpf@kernel.org
To: None <liuyacan@corp.netease.com>
Cc: wenjia@linux.ibm.com, davem@davemloft.net, edumazet@google.com,
kgraul@linux.ibm.com, kuba@kernel.org, tonylu@linux.alibaba.com,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
ubraun@linux.vnet.ibm.com, wintera@linux.ibm.com
Subject: Re: [PATCH net v5] net/smc: Fix possible access to freed memory in link clear
Date: Wed, 07 Sep 2022 15:10:14 +0000 [thread overview]
Message-ID: <166256341452.32760.12403709624294959610.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220906130139.830513-1-liuyacan@corp.netease.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 6 Sep 2022 21:01:39 +0800 you wrote:
> From: Yacan Liu <liuyacan@corp.netease.com>
>
> After modifying the QP to the Error state, all RX WR would be completed
> with WC in IB_WC_WR_FLUSH_ERR status. Current implementation does not
> wait for it is done, but destroy the QP and free the link group directly.
> So there is a risk that accessing the freed memory in tasklet context.
>
> [...]
Here is the summary with links:
- [net,v5] net/smc: Fix possible access to freed memory in link clear
https://git.kernel.org/netdev/net/c/e9b1a4f867ae
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-09-07 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 13:01 [PATCH net v5] net/smc: Fix possible access to freed memory in link clear liuyacan
2022-09-07 15: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=166256341452.32760.12403709624294959610.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=tonylu@linux.alibaba.com \
--cc=ubraun@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox