Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp753788ybe; Fri, 6 Sep 2019 06:51:40 -0700 (PDT) X-Google-Smtp-Source: APXvYqxQQJK1r6Tv0CM99ECWG0b2ZBMvnMV3ei5L4vi0nS93XTvzIApfOWtelpig4Bx6dNyGbnah X-Received: by 2002:a17:902:424:: with SMTP id 33mr9432715ple.34.1567777900095; Fri, 06 Sep 2019 06:51:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567777900; cv=none; d=google.com; s=arc-20160816; b=MGT2s9MqEYGJnQU/7H0qQKHDaugBUro9JxsfECNxYEw4xlLs+pu+5UIVsyEjoYFVw9 X2VecrPZWjz1naZ8I2Zjxzc9qdm9fazpaIsUrgtePQulbeHXWcA4GQ5eIEo6k1BzX6fA eOwGw4ONgGFePw/+ZrmuLioyJc7k8EIdw3fDQ5rRGDzjGs3afbWWduu6ss6rYlfEE1+M DfpDAM436W6EAsGTOm5GgmqFYhLF2ZldnaTh0QF271RRr2wzzpIjYngarU7AWIlqHSdm kGohkuYSTvM7ezNhPf9QQYqkre7kB93ng+a7WmSP9/Od0YF2kM33dAyatCsBpSRBqsLN JpjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=OaQpfgWg82Gbx9pj05M6vHbSkCWlZTT/kV9LTekh3Q8=; b=rTHte02OnMr3lzExlaFADguNtux8+yVzXXdWp9+ibhcpwMd7eLJzq597sSRphepc/H 2lgOzMsOKLlvp7+PeBCpom1/liQNPeEUsxGUOadzih+g5zSY8F6Krm2gOglD7lVtqtND D5VedYgWeCc/+LWcQvbDATTS5k1krn9m5VXXk+TyC5ao8xbznWqTTP8S4BUugEB3i18m 0/vRnKYDc3Rk2yHnttKxO0wc28tJLXNzJpPdL1yK7wQ9KYlJ5Ou9cjPuI5VnfuRRg/Sp jwyqWvYBbAFe4pTHh5XV0uLThQr/y/WKDoleffRqbGuPYPLCYutWvp+xEaMWmTmhOnwX nl3Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a13si4385965pgt.217.2019.09.06.06.51.22; Fri, 06 Sep 2019 06:51:40 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390803AbfIFHN7 (ORCPT + 99 others); Fri, 6 Sep 2019 03:13:59 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:56458 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726115AbfIFHN6 (ORCPT ); Fri, 6 Sep 2019 03:13:58 -0400 Received: from localhost (unknown [88.214.187.128]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id E584E15163DE2; Fri, 6 Sep 2019 00:13:56 -0700 (PDT) Date: Fri, 06 Sep 2019 09:13:50 +0200 (CEST) Message-Id: <20190906.091350.2133455010162259391.davem@davemloft.net> To: enkechen@cisco.com Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, xe-linux-external@cisco.com Subject: Re: [PATCH] net: Remove the source address setting in connect() for UDP From: David Miller In-Reply-To: <20190906025437.613-1-enkechen@cisco.com> References: <20190906025437.613-1-enkechen@cisco.com> X-Mailer: Mew version 6.8 on Emacs 26.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Fri, 06 Sep 2019 00:13:58 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Enke Chen Date: Thu, 5 Sep 2019 19:54:37 -0700 > The connect() system call for a UDP socket is for setting the destination > address and port. But the current code mistakenly sets the source address > for the socket as well. Remove the source address setting in connect() for > UDP in this patch. Do you have any idea how many decades of precedence this behavior has and therefore how much you potentially will break userspace? This boat has sailed a long time ago I'm afraid.