From: Dust Li <dust.li@linux.alibaba.com>
To: Mahanta Jambigi <mjambigi@linux.ibm.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: Fri, 29 Aug 2025 22:58:11 +0800 [thread overview]
Message-ID: <aLHAAy-S_1_Ud7l-@linux.alibaba.com> (raw)
In-Reply-To: <20250829102626.3271637-1-mjambigi@linux.ibm.com>
On 2025-08-29 12:26:26, Mahanta Jambigi wrote:
>Currently SMC code is validating the reserved bits while parsing the incoming
>CLC decline message & when this validation fails, its treated as a protocol
>error. As a result, the SMC connection is terminated instead of falling back to
>TCP. As per RFC7609[1] specs we shouldn't be validating the reserved bits that
>is part of CLC message. This patch fixes this issue.
>
>CLC Decline message format can viewed here[2].
>
>[1] https://datatracker.ietf.org/doc/html/rfc7609#page-92
>[2] https://datatracker.ietf.org/doc/html/rfc7609#page-105
>
>Fixes: 8ade200(net/smc: add v2 format of CLC decline message)
>
>Signed-off-by: Mahanta Jambigi <mjambigi@linux.ibm.com>
>Reference-ID: LTC214332
I think this is your internal ID ? It's better not to leave that
in the upstream patches.
>Reviewed-by: Sidraya Jayagond <sidraya@linux.ibm.com>
>Reviewed-by: Alexandra Winter <wintera@linux.ibm.com>
>
>---
> net/smc/smc_clc.c | 2 --
> 1 file changed, 2 deletions(-)
>
>diff --git a/net/smc/smc_clc.c b/net/smc/smc_clc.c
>index 5a4db151fe95..08be56dfb3f2 100644
>--- a/net/smc/smc_clc.c
>+++ b/net/smc/smc_clc.c
>@@ -426,8 +426,6 @@ smc_clc_msg_decl_valid(struct smc_clc_msg_decline *dclc)
> {
> struct smc_clc_msg_hdr *hdr = &dclc->hdr;
>
>- if (hdr->typev1 != SMC_TYPE_R && hdr->typev1 != SMC_TYPE_D)
>- return false;
Here it's checking the typev1 in smc_clc_msg_hdr, but your commit message
says it's validating the reserved bits:
Currently SMC code is validating the reserved bits while parsing the incoming
CLC decline message & when this validation fails, its treated as a protocol
error.
Did I miss something ?
Best regards,
Dust
next prev parent reply other threads:[~2025-08-29 14:58 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 [this message]
2025-09-01 6:12 ` Mahanta Jambigi
2025-09-02 4:08 ` Dust Li
2025-09-02 6:05 ` Mahanta Jambigi
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=aLHAAy-S_1_Ud7l-@linux.alibaba.com \
--to=dust.li@linux.alibaba.com \
--cc=alibuda@linux.alibaba.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--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=mjambigi@linux.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.