From: "D. Wythe" <alibuda@linux.alibaba.com>
To: Wen Gu <guwen@linux.alibaba.com>, kgraul@linux.ibm.com
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next] net/smc: Fix smc-r link reference count
Date: Fri, 6 May 2022 17:47:29 +0800 [thread overview]
Message-ID: <90cf2e6b-e409-7f52-bde3-ebb93994b931@linux.alibaba.com> (raw)
In-Reply-To: <e3dbf77b-777a-8b6b-3c52-d1bb3f385c26@linux.alibaba.com>
在 2022/5/6 下午3:58, Wen Gu 写道:
> Thanks for your analysis.
>
> 1) Is the patch more appropriate to 'net' ?
That's my mistake.
> 2) The refcnt of smc link will be
>
> - initilized to 1 in smcr_link_init();
>
> - increased when connections assigned to the link;
> eg. smc_conn_create() or smc_switch_link_and_count();
>
> - decreased when connections removed from the link or link is cleared,
> eg. smc_conn_free(), smc_switch_link_and_count(), smcr_link_clear().
>
> I see the theoretical race between smcr_link_hold() and
> smcr_link_put(). Have you encountered this
> issue in actual test, such as triggering WARN of refcount_inc()?
> Because IMHO the race window is small
> (link state will turned to SMC_LNK_UNUSED after smcr_link_put() and
> connections will not be assigned to it).
>
>
Got your point, this race may happened with our another radical change.
At present, this patch may not be needed.
Thanks.
D. Wythe
prev parent reply other threads:[~2022-05-06 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 5:22 [PATCH net-next] net/smc: Fix smc-r link reference count D. Wythe
2022-05-06 6:47 ` D. Wythe
2022-05-06 7:58 ` Wen Gu
2022-05-06 9:47 ` D. Wythe [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=90cf2e6b-e409-7f52-bde3-ebb93994b931@linux.alibaba.com \
--to=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=guwen@linux.alibaba.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 \
/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;
as well as URLs for NNTP newsgroup(s).