aboutsummaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
authorMahanta Jambigi <mjambigi@linux.ibm.com>2025-09-02 10:20:41 +0200
committerJakub Kicinski <kuba@kernel.org>2025-09-03 17:01:07 -0700
commitcc282f73bc0cbdf3ee7af2f2d3a2ef4e6b19242d (patch)
tree17e69e88a7af920b5b2c9bf32234f11fe3846402
parentipv4: Fix NULL vs error pointer check in inet_blackhole_dev_init() (diff)
downloadwireguard-linux-cc282f73bc0cbdf3ee7af2f2d3a2ef4e6b19242d.tar.xz
wireguard-linux-cc282f73bc0cbdf3ee7af2f2d3a2ef4e6b19242d.zip
net/smc: Remove validation of reserved bits in CLC Decline message
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: 8ade200c269f ("net/smc: add v2 format of CLC decline message") Signed-off-by: Mahanta Jambigi <mjambigi@linux.ibm.com> Reviewed-by: Sidraya Jayagond <sidraya@linux.ibm.com> Reviewed-by: Alexandra Winter <wintera@linux.ibm.com> Reviewed-by: Dust Li <dust.li@linux.alibaba.com> Link: https://patch.msgid.link/20250902082041.98996-1-mjambigi@linux.ibm.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
-rw-r--r--net/smc/smc_clc.c2
1 files changed, 0 insertions, 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;
if (hdr->version == SMC_V1) {
if (ntohs(hdr->length) != sizeof(struct smc_clc_msg_decline))
return false;