From: Wen Gu <guwen@linux.alibaba.com>
To: Alexandra Winter <wintera@linux.ibm.com>,
wenjia@linux.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com,
agordeev@linux.ibm.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, jaka@linux.ibm.com,
Matthew Rosato <mjrosato@linux.ibm.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
borntraeger@linux.ibm.com, svens@linux.ibm.com,
alibuda@linux.alibaba.com, tonylu@linux.alibaba.com,
raspl@linux.ibm.com, schnelle@linux.ibm.com,
guangguan.wang@linux.alibaba.com, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [REGRESSION] v6.8 SMC-D issues
Date: Thu, 25 Jan 2024 12:59:41 +0800 [thread overview]
Message-ID: <530afe45-ba6b-4970-a71c-1f1255f5fca9@linux.alibaba.com> (raw)
In-Reply-To: <13579588-eb9d-4626-a063-c0b77ed80f11@linux.ibm.com>
On 2024/1/24 22:29, Alexandra Winter wrote:
> Hello Wen Gu,
>
> our colleague Matthew reported that SMC-D is failing in certain scenarios on
> kernel v6.8 (thx Matt!). He bisected it to
> b40584d ("net/smc: compatible with 128-bits extended GID of virtual ISM device")
> I think the root cause could also be somewhere else in the SMC-Dv2.1 patchset.
>
> I was able to reproduce the issue on a 6.8.0-rc1 kernel.
> I tested iperf over smc-d with:
> smc_run iperf3 -s
> smc_run iperf3 -c <IP@>
>
> 1) Doing an iperf in a single system using 127.0.0.1 as IP@
> (System A=iperf client=iperf server)
> 2) Doing iperf to a remote system (System A=client; System B=iperf server)
>
> The second iperf fails with an error message like:
> "iperf3: error - unable to receive cookie at server: Bad file descriptor" on the server"
>
> If I do first 2) (iperf to remote) and then 1) (iperf to local), then the
> iperf to local fails.
>
> I can do multiple iperf to the first server without problems.
>
> I ran it on a debug server with KASAN, but got no reports in the Logfile.
>
> I will try to debug further, but wanted to let you all know.
>
> Kind regards
> Alexandra
>
> Reported-by: Matthew Rosato <mjrosato@linux.ibm.com>
>
Hi Alexandra and Matthew,
Thank you very much for detailed description.
I tried to reproduce this with loopback-ism, cut some checks so that the remote-system
handshake can be done. After a while debug I found an elementary mistake of mine in
b40584d ("net/smc: compatible with 128-bits extended GID of virtual ISM device")..
The operator order in smcd_lgr_match() is not as expected. It will always return
'true' in remote-system case.
static bool smcd_lgr_match(struct smc_link_group *lgr,
- struct smcd_dev *smcismdev, u64 peer_gid)
+ struct smcd_dev *smcismdev,
+ struct smcd_gid *peer_gid)
{
- return lgr->peer_gid == peer_gid && lgr->smcd == smcismdev;
+ return lgr->peer_gid.gid == peer_gid->gid && lgr->smcd == smcismdev &&
+ smc_ism_is_virtual(smcismdev) ?
+ (lgr->peer_gid.gid_ext == peer_gid->gid_ext) : 1;
}
Could you please try again with this patch? to see if this is the root cause.
Really sorry for the inconvenience.
diff --git a/net/smc/smc_core.c b/net/smc/smc_core.c
index da6a8d9c81ea..c6a6ba56c9e3 100644
--- a/net/smc/smc_core.c
+++ b/net/smc/smc_core.c
@@ -1896,8 +1896,8 @@ static bool smcd_lgr_match(struct smc_link_group *lgr,
struct smcd_gid *peer_gid)
{
return lgr->peer_gid.gid == peer_gid->gid && lgr->smcd == smcismdev &&
- smc_ism_is_virtual(smcismdev) ?
- (lgr->peer_gid.gid_ext == peer_gid->gid_ext) : 1;
+ (smc_ism_is_virtual(smcismdev) ?
+ (lgr->peer_gid.gid_ext == peer_gid->gid_ext) : 1);
}
Thanks,
Wen Gu
next prev parent reply other threads:[~2024-01-25 4:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 14:26 [PATCH net-next v8 00/10] net/smc: implement SMCv2.1 virtual ISM device support Wen Gu
2023-12-19 14:26 ` [PATCH net-next v8 01/10] net/smc: rename some 'fce' to 'fce_v2x' for clarity Wen Gu
2023-12-19 14:26 ` [PATCH net-next v8 02/10] net/smc: introduce sub-functions for smc_clc_send_confirm_accept() Wen Gu
2023-12-19 14:26 ` [PATCH net-next v8 03/10] net/smc: unify the structs of accept or confirm message for v1 and v2 Wen Gu
2023-12-20 10:27 ` Alexandra Winter
2023-12-20 11:37 ` Alexandra Winter
2023-12-20 12:16 ` Wen Gu
2023-12-19 14:26 ` [PATCH net-next v8 04/10] net/smc: support SMCv2.x supplemental features negotiation Wen Gu
2023-12-19 14:26 ` [PATCH net-next v8 05/10] net/smc: introduce virtual ISM device support feature Wen Gu
2023-12-19 14:26 ` [PATCH net-next v8 06/10] net/smc: define a reserved CHID range for virtual ISM devices Wen Gu
2023-12-19 14:26 ` [PATCH net-next v8 07/10] net/smc: compatible with 128-bits extended GID of virtual ISM device Wen Gu
2024-01-24 14:29 ` [REGRESSION] v6.8 SMC-D issues Alexandra Winter
2024-01-24 14:44 ` Alexandra Winter
2024-01-25 4:59 ` Wen Gu [this message]
2024-01-25 8:26 ` Alexandra Winter
2024-01-25 9:28 ` Wen Gu
2023-12-19 14:26 ` [PATCH net-next v8 08/10] net/smc: support extended GID in SMC-D lgr netlink attribute Wen Gu
2023-12-19 14:26 ` [PATCH net-next v8 09/10] net/smc: disable SEID on non-s390 archs where virtual ISM may be used Wen Gu
2023-12-19 14:26 ` [PATCH net-next v8 10/10] net/smc: manage system EID in SMC stack instead of ISM driver Wen Gu
2023-12-20 13:34 ` [PATCH net-next v8 00/10] net/smc: implement SMCv2.1 virtual ISM device support Wen Gu
2023-12-26 20:30 ` patchwork-bot+netdevbpf
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=530afe45-ba6b-4970-a71c-1f1255f5fca9@linux.alibaba.com \
--to=guwen@linux.alibaba.com \
--cc=agordeev@linux.ibm.com \
--cc=alibuda@linux.alibaba.com \
--cc=borntraeger@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gor@linux.ibm.com \
--cc=guangguan.wang@linux.alibaba.com \
--cc=hca@linux.ibm.com \
--cc=jaka@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=raspl@linux.ibm.com \
--cc=regressions@lists.linux.dev \
--cc=schnelle@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@linux.ibm.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