From: Simon Horman <horms@kernel.org>
To: Wen Gu <guwen@linux.alibaba.com>
Cc: 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,
kgraul@linux.ibm.com, jaka@linux.ibm.com,
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
Subject: Re: [PATCH net-next v7 07/10] net/smc: compatible with 128-bits extended GID of virtual ISM device
Date: Tue, 19 Dec 2023 11:59:52 +0000 [thread overview]
Message-ID: <20231219115952.GL811967@kernel.org> (raw)
In-Reply-To: <20231219084536.8158-8-guwen@linux.alibaba.com>
On Tue, Dec 19, 2023 at 04:45:33PM +0800, Wen Gu wrote:
> According to virtual ISM support feature defined by SMCv2.1, GIDs of
> virtual ISM device are UUIDs defined by RFC4122, which are 128-bits
> long. So some adaptation work is required. And note that the GIDs of
> existing platform firmware ISM devices still remain 64-bits long.
>
> Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
> Reviewed-by: Alexandra Winter <wintera@linux.ibm.com>
...
> @@ -1023,9 +1041,12 @@ smcd_clc_prep_confirm_accept(struct smc_connection *conn,
> if (version == SMC_V1) {
> clc->hdr.length = htons(SMCD_CLC_ACCEPT_CONFIRM_LEN);
> } else {
> - clc->d1.chid = htons(smc_ism_get_chid(smcd));
> + chid = smc_ism_get_chid(smcd);
> + clc->d1.chid = htons(chid);
> if (eid && eid[0])
> memcpy(clc->d1.eid, eid, SMC_MAX_EID_LEN);
> + if (__smc_ism_is_virtual(chid))
> + clc->d1.gid_ext = htonll(smcd_gid.gid_ext);
Hi Wen Gu,
The type of clc->d1.gid_ext is u64 (host byte-order)
but here it is being assigned a big endian value.
This does not seem correct.
Flagged by Smatch.
> len = SMCD_CLC_ACCEPT_CONFIRM_LEN_V2;
> if (first_contact) {
> *fce_len = smc_clc_fill_fce_v2x(fce_v2x, ini);
...
--
pw-bot: changes-requested
next prev parent reply other threads:[~2023-12-19 11:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 8:45 [PATCH net-next v7 00/10] net/smc: implement SMCv2.1 virtual ISM device support Wen Gu
2023-12-19 8:45 ` [PATCH net-next v7 01/10] net/smc: rename some 'fce' to 'fce_v2x' for clarity Wen Gu
2023-12-19 8:45 ` [PATCH net-next v7 02/10] net/smc: introduce sub-functions for smc_clc_send_confirm_accept() Wen Gu
2023-12-19 8:45 ` [PATCH net-next v7 03/10] net/smc: unify the structs of accept or confirm message for v1 and v2 Wen Gu
2023-12-19 8:45 ` [PATCH net-next v7 04/10] net/smc: support SMCv2.x supplemental features negotiation Wen Gu
2023-12-19 8:45 ` [PATCH net-next v7 05/10] net/smc: introduce virtual ISM device support feature Wen Gu
2023-12-19 8:45 ` [PATCH net-next v7 06/10] net/smc: define a reserved CHID range for virtual ISM devices Wen Gu
2023-12-19 8:45 ` [PATCH net-next v7 07/10] net/smc: compatible with 128-bits extended GID of virtual ISM device Wen Gu
2023-12-19 11:59 ` Simon Horman [this message]
2023-12-19 12:22 ` Wen Gu
2023-12-19 8:45 ` [PATCH net-next v7 08/10] net/smc: support extended GID in SMC-D lgr netlink attribute Wen Gu
2023-12-19 8:45 ` [PATCH net-next v7 09/10] net/smc: disable SEID on non-s390 archs where virtual ISM may be used Wen Gu
2023-12-19 8:45 ` [PATCH net-next v7 10/10] net/smc: manage system EID in SMC stack instead of ISM driver 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=20231219115952.GL811967@kernel.org \
--to=horms@kernel.org \
--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=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=pabeni@redhat.com \
--cc=raspl@linux.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).