From: Mahanta Jambigi <mjambigi@linux.ibm.com>
To: dust.li@linux.alibaba.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, alibuda@linux.alibaba.com,
sidraya@linux.ibm.com, wenjia@linux.ibm.com
Cc: pasic@linux.ibm.com, horms@kernel.org, tonylu@linux.alibaba.com,
guwen@linux.alibaba.com, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
Alexandra Winter <wintera@linux.ibm.com>
Subject: Re: [PATCH net] net/smc: Remove validation of reserved bits in CLC Decline message
Date: Tue, 2 Sep 2025 11:35:34 +0530 [thread overview]
Message-ID: <8a795b8c-5613-4952-a5fc-59cead205e59@linux.ibm.com> (raw)
In-Reply-To: <aLZtraICmwOQAtsO@linux.alibaba.com>
On 02/09/25 9:38 am, Dust Li wrote:
>>>
>>> Did I miss something ?
>>
>> If you refer to struct *smc_clc_msg_hdr* in smc_clc.h file, typev1 member
>> represents bits 4 & 5 at offset 7. If we compare it with the CLC Decline
>> message header, it represents one of the reserved(5-7 bits) at offset 7. You
>> can refer to below link for reserved bits.
>>
>> https://datatracker.ietf.org/doc/html/rfc7609#page-105
>
> Oh, I see, thanks! The patch looks good to me.
>
>
> BTW, I checked the rfc7609 and SMCv2.1 spec:
> https://www.ibm.com/support/pages/system/files/inline-files/IBM%20Shared%20Memory%20Communications%20Version%202.1_0.pdf
>
> I think the name type1/type2 in smc_clc_msg_hdr is confusing, as it doesn't sync
> with the spec for decline message.
I agree with you. We can address them in future. Since they are part of
reserved bits, we can ignore parsing them for now. May I add your R-b
for this patch?
>
> Best regards,
> Dust
>
>
next prev parent reply other threads:[~2025-09-02 6:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 10:26 [PATCH net] net/smc: Remove validation of reserved bits in CLC Decline message Mahanta Jambigi
2025-08-29 14:58 ` Dust Li
2025-09-01 6:12 ` Mahanta Jambigi
2025-09-02 4:08 ` Dust Li
2025-09-02 6:05 ` Mahanta Jambigi [this message]
2025-09-02 7:26 ` Dust Li
2025-09-02 7:08 ` Simon Horman
2025-09-02 8:13 ` Mahanta Jambigi
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=8a795b8c-5613-4952-a5fc-59cead205e59@linux.ibm.com \
--to=mjambigi@linux.ibm.com \
--cc=alibuda@linux.alibaba.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=sidraya@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).