From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net] sctp: do not check port in sctp_inet6_cmp_addr Date: Wed, 11 Apr 2018 12:40:43 -0400 (EDT) Message-ID: <20180411.124043.1093527105189345576.davem@davemloft.net> References: <20180411143607.GA4141@hmswarspite.think-freely.org> <20180411145910.GC3711@localhost.localdomain> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: marcelo.leitner@gmail.com, nhorman@tuxdriver.com, netdev@vger.kernel.org, linux-sctp@vger.kernel.org To: lucien.xin@gmail.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:42802 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753411AbeDKQkr (ORCPT ); Wed, 11 Apr 2018 12:40:47 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Xin Long Date: Thu, 12 Apr 2018 00:16:58 +0800 > What do you think of: > > static int sctp_v6_cmp_addr(const union sctp_addr *addr1, > const union sctp_addr *addr2) > { > return __sctp_v6_cmp_addr(addr1, addr2) && > addr1->v6.sin_port == addr2->v6.sin_port; > } > > (v6.sin_port and v4.sin_port have the same offset in union sctp_addr, > we've exploited this in many places in SCTP) >>From my perspective this is OK. From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Date: Wed, 11 Apr 2018 16:40:43 +0000 Subject: Re: [PATCH net] sctp: do not check port in sctp_inet6_cmp_addr Message-Id: <20180411.124043.1093527105189345576.davem@davemloft.net> List-Id: References: <20180411143607.GA4141@hmswarspite.think-freely.org> <20180411145910.GC3711@localhost.localdomain> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lucien.xin@gmail.com Cc: marcelo.leitner@gmail.com, nhorman@tuxdriver.com, netdev@vger.kernel.org, linux-sctp@vger.kernel.org From: Xin Long Date: Thu, 12 Apr 2018 00:16:58 +0800 > What do you think of: > > static int sctp_v6_cmp_addr(const union sctp_addr *addr1, > const union sctp_addr *addr2) > { > return __sctp_v6_cmp_addr(addr1, addr2) && > addr1->v6.sin_port = addr2->v6.sin_port; > } > > (v6.sin_port and v4.sin_port have the same offset in union sctp_addr, > we've exploited this in many places in SCTP) >From my perspective this is OK.