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,
	dust.li@linux.alibaba.com, linux-s390@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net/smc: Fix hung_task when removing SMC-R devices
Date: Sun, 16 Jan 2022 12:40:08 +0000	[thread overview]
Message-ID: <164233680869.3883.15974762125113238993.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1642319022-99525-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 Sun, 16 Jan 2022 15:43:42 +0800 you wrote:
> A hung_task is observed when removing SMC-R devices. Suppose that
> a link group has two active links(lnk_A, lnk_B) associated with two
> different SMC-R devices(dev_A, dev_B). When dev_A is removed, the
> link group will be removed from smc_lgr_list and added into
> lgr_linkdown_list. lnk_A will be cleared and smcibdev(A)->lnk_cnt
> will reach to zero. However, when dev_B is removed then, the link
> group can't be found in smc_lgr_list and lnk_B won't be cleared,
> making smcibdev->lnk_cnt never reaches zero, which causes a hung_task.
> 
> [...]

Here is the summary with links:
  - [net,v2] net/smc: Fix hung_task when removing SMC-R devices
    https://git.kernel.org/netdev/net/c/56d99e81ecbc

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



      reply	other threads:[~2022-01-16 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-16  7:43 [PATCH net v2] net/smc: Fix hung_task when removing SMC-R devices Wen Gu
2022-01-16 12:40 ` 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=164233680869.3883.15974762125113238993.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dust.li@linux.alibaba.com \
    --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