public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Wen Gu <guwen@linux.alibaba.com>
Cc: kgraul@linux.ibm.com, davem@davemloft.net, kuba@kernel.org,
	linux-s390@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v5] net/smc: Reset conn->lgr when link group registration fails
Date: Thu, 06 Jan 2022 14:00:10 +0000	[thread overview]
Message-ID: <164147761013.14327.180691218581013319.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1641472928-55944-1-git-send-email-guwen@linux.alibaba.com>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Thu,  6 Jan 2022 20:42:08 +0800 you wrote:
> SMC connections might fail to be registered in a link group due to
> unable to find a usable link during its creation. As a result,
> smc_conn_create() will return a failure and most resources related
> to the connection won't be applied or initialized, such as
> conn->abort_work or conn->lnk.
> 
> If smc_conn_free() is invoked later, it will try to access the
> uninitialized resources related to the connection, thus causing
> a warning or crash.
> 
> [...]

Here is the summary with links:
  - [net,v5] net/smc: Reset conn->lgr when link group registration fails
    https://git.kernel.org/netdev/net/c/36595d8ad46d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-01-06 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 12:42 [PATCH net v5] net/smc: Reset conn->lgr when link group registration fails Wen Gu
2022-01-06 12:51 ` Karsten Graul
2022-01-06 14:00 ` 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=164147761013.14327.180691218581013319.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=guwen@linux.alibaba.com \
    --cc=kgraul@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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