From: Alexandra Winter <wintera@linux.ibm.com>
To: Wen Gu <guwen@linux.alibaba.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 09:26:59 +0100 [thread overview]
Message-ID: <8090bb34-1b70-43ea-ae13-df5d9a5eb761@linux.ibm.com> (raw)
In-Reply-To: <530afe45-ba6b-4970-a71c-1f1255f5fca9@linux.alibaba.com>
On 25.01.24 05:59, Wen Gu wrote:
> 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
Hello Wen Gu,
thank you for the quick resposne and for finding this nasty bug.
I can confirm that with your patch I do not see the issue anymore.
Please send a fix to the mailing lists. See
https://docs.kernel.org/process/handling-regressions.html
for some tips.
May I propose that instead of adding the brackets, you change this function
to an if-then-else sequence for readability and maintainability?
I would still mention the missing brackets in the commit message, so
readers can quickly understand the issue.
Thanks again for the quick response.
Sandy
next prev parent reply other threads:[~2024-01-25 8:30 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
2024-01-25 8:26 ` Alexandra Winter [this message]
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=8090bb34-1b70-43ea-ae13-df5d9a5eb761@linux.ibm.com \
--to=wintera@linux.ibm.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=guwen@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 \
/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