public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wen Gu <guwen@linux.alibaba.com>
To: kgraul@linux.ibm.com, davem@davemloft.net, kuba@kernel.org
Cc: linux-s390@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, dust.li@linux.alibaba.com,
	tonylu@linux.alibaba.com
Subject: [RFC PATCH net v2 0/2] net/smc: Fix for race in smc link group termination
Date: Tue, 28 Dec 2021 23:13:50 +0800	[thread overview]
Message-ID: <1640704432-76825-1-git-send-email-guwen@linux.alibaba.com> (raw)

We encountered some crashes recently and they are caused by the
race between the access and free of link/link group in smc link
group termination. The crashes can be reproduced in frequent
abnormal link group termination, like set RNICs up/down.

This set of patches tries to fix this by extending the life cycle
of link/link group to ensure that they won't be referred to after
cleared or freed.

v1->v2
- Declare __smcr_link_clear() as 'static'

Best wishes,
Wen Gu

Wen Gu (2):
  net/smc: Resolve the race between link group access and termination
  net/smc: Resolve the race between SMC-R link access and clear

 net/smc/smc.h      |  1 +
 net/smc/smc_core.c | 80 ++++++++++++++++++++++++++++++++++++++++++++++++------
 net/smc/smc_core.h |  7 +++++
 3 files changed, 79 insertions(+), 9 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2021-12-28 15:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-28 15:13 Wen Gu [this message]
2021-12-28 15:13 ` [RFC PATCH net v2 1/2] net/smc: Resolve the race between link group access and termination Wen Gu
2021-12-29 12:56   ` Karsten Graul
2021-12-31  9:44     ` Wen Gu
2022-01-03 10:36       ` Karsten Graul
2022-01-05  8:27         ` Wen Gu
2022-01-05 12:03           ` Karsten Graul
2022-01-06 13:02             ` Wen Gu
2022-01-07  9:54               ` Karsten Graul
2022-01-07 12:04                 ` Wen Gu
2021-12-28 15:13 ` [RFC PATCH net v2 2/2] net/smc: Resolve the race between SMC-R link access and clear Wen Gu
2021-12-29 12:51   ` Karsten Graul
2021-12-30  4:00     ` dust.li
2021-12-31  9:45     ` Wen Gu
2022-01-03 10:39       ` 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=1640704432-76825-1-git-send-email-guwen@linux.alibaba.com \
    --to=guwen@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=dust.li@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 \
    --cc=tonylu@linux.alibaba.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