From: Wen Gu <guwen@linux.alibaba.com>
To: kgraul@linux.ibm.com, tonylu@linux.alibaba.com
Cc: davem@davemloft.net, kuba@kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
dust.li@linux.alibaba.com, xuanzhuo@linux.alibaba.com,
guwen@linux.alibaba.com
Subject: [RFC PATCH 0/2] Two RFC patches for the same SMC socket wait queue mismatch issue
Date: Wed, 10 Nov 2021 20:50:49 +0800 [thread overview]
Message-ID: <1636548651-44649-1-git-send-email-guwen@linux.alibaba.com> (raw)
Hi, Karsten
Thanks for your reply. The previous discussion about the issue of socket
wait queue mismatch in SMC fallback can be referred from:
https://lore.kernel.org/all/db9acf73-abef-209e-6ec2-8ada92e2cfbc@linux.ibm.com/
This set of patches includes two RFC patches, they are both aimed to fix
the same issue, the mismatch of socket wait queue in SMC fallback.
In your last reply, I am suggested to add the complete description about
the intention of initial patch in order that readers can understand the
idea behind it. This has been done in "[RFC PATCH net v2 0/2] net/smc: Fix
socket wait queue mismatch issue caused by fallback" of this mail.
Unfortunately, I found a defect later in the solution of the initial patch
or the v2 patch mentioned above. The defect is about fasync_list and related
to 67f562e3e14 ("net/smc: transfer fasync_list in case of fallback").
When user applications use sock_fasync() to insert entries into fasync_list,
the wait queue they operate is smc socket->wq. But in initial patch or
the v2 patch, I swapped sk->sk_wq of smc socket and clcsocket in smc_create(),
thus the sk_data_ready / sk_write_space.. of smc will wake up clcsocket->wq
finally. So the entries added into smc socket->wq.fasync_list won't be woken
up at all before fallback.
So the solution in initial patch or the v2 patch of this mail by swapping
sk->sk_wq of smc socket and clcsocket seems a bad way to fix this issue.
Therefore, I tried another solution by removing the wait queue entries from
smc socket->wq to clcsocket->wq during the fallback, which is described in the
"[RFC PATCH net 2/2] net/smc: Transfer remaining wait queue entries" of this
mail. In our test environment, this patch can fix the fallback issue well.
I am looking forward to hear your opinions. Thank you.
Cheers,
Wen Gu
Wen Gu (2):
net/smc: Fix socket wait queue mismatch issue caused by fallback
net/smc: Transfer remaining wait queue entries
next reply other threads:[~2021-11-10 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 12:50 Wen Gu [this message]
2021-11-10 12:50 ` [RFC PATCH net v2 1/2] net/smc: Fix socket wait queue mismatch issue caused by fallback Wen Gu
2021-11-10 12:50 ` [RFC PATCH net 2/2] net/smc: Transfer remaining wait queue entries during fallback Wen Gu
2021-11-11 14:21 ` [RFC PATCH 0/2] Two RFC patches for the same SMC socket wait queue mismatch issue Karsten Graul
2021-11-12 3:09 ` Wen Gu
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=1636548651-44649-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 \
--cc=xuanzhuo@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