Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp283073ybl; Thu, 29 Aug 2019 23:05:14 -0700 (PDT) X-Google-Smtp-Source: APXvYqz5egFbGITnsA6Q1pUGKqgNUot6xQH2Fe3llWcx1TDgkoC7RISww+2QOcy0ioKFmjSFVrSj X-Received: by 2002:a17:902:a01:: with SMTP id 1mr14300272plo.278.1567145114515; Thu, 29 Aug 2019 23:05:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567145114; cv=none; d=google.com; s=arc-20160816; b=HhQiRCu7b4j+RwVBl+Iu/sSpfPs4gIzgRSVMpdYNoWF8Nq01PQsdKbq8BcHMWrakC9 e6Lw9xnxIY8jpy+jGqgTx7pY+58nMtsAj4r6q3O1uDNk6u2WIVDUNpz4ptkh/R8XvxF4 jKvhMSOxUwFj7JCncnrYWUReAcLDdJgD1gZIWXCNVT0b1uYJkraE++uTcuaqJ0nw1EQ+ 3YnsF36hqqc6SDrcl1T0/9b4qz626LEnVlD/OHMHJ8mqrH5lBt2MNDSos+8dfUbMzbGj V/CRvf6ajmw1ZaqJrBRipBVXpFfmIfR5b6NmmwQqwNZ8Mmj/woYqqkcDBrk6SF5NnD+3 VqBw== 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=wbJ4Wqt4DWe+Y71qUSPAejxnlu1eDu+E/KHTR6eXXho=; b=GN5XXQqFE7hJc364g78wQrDHtVRf0MMp1sQ7GFF6ZxoOyj2LMpqx/VlpT6zmPJs6l4 WGCVvwILbxoyExQap9YVHxrYWewlcCmWkg46robk9Nyq8dVXmfM8Q5/4xc4bk8XfAhCE C47EiebuF9CglRTZNiuqRf3NxZ4n3riJsleHFxab7EJnBcVSNm+Bu2XU2cCERRY+wHx4 3YiEvjjDpF3y0dvrHL0Lbe7NcsGhFHfNla0HWhEgBsECNQWMlb353LtGshZV9+SdqwTB YtzP1iKTFYYh3HBiHUW20IAxjHhPiVBvgQH1NGxjz3zwlvA4AtCRtOIvs9GrtZU5u69G Ttgg== 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 j1si3790678pgk.187.2019.08.29.23.04.58; Thu, 29 Aug 2019 23:05:14 -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 S1727933AbfH3GCe (ORCPT + 99 others); Fri, 30 Aug 2019 02:02:34 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:58946 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727718AbfH3GCe (ORCPT ); Fri, 30 Aug 2019 02:02:34 -0400 Received: from localhost (unknown [IPv6:2601:601:9f80:35cd::d71]) (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 A3B7E15447999; Thu, 29 Aug 2019 23:02:33 -0700 (PDT) Date: Thu, 29 Aug 2019 23:02:33 -0700 (PDT) Message-Id: <20190829.230233.287975311556641534.davem@davemloft.net> To: jiri@resnulli.us Cc: idosch@idosch.org, andrew@lunn.ch, horatiu.vultur@microchip.com, alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com, allan.nielsen@microchip.com, ivecera@redhat.com, f.fainelli@gmail.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 1/2] net: core: Notify on changes to dev->promiscuity. From: David Miller In-Reply-To: <20190830053940.GL2312@nanopsycho> References: <20190829193613.GA23259@splinter> <20190829.151201.940681219080864052.davem@davemloft.net> <20190830053940.GL2312@nanopsycho> X-Mailer: Mew version 6.8 on Emacs 26.1 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]); Thu, 29 Aug 2019 23:02:34 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Jiri Pirko Date: Fri, 30 Aug 2019 07:39:40 +0200 > Because the "promisc mode" would gain another meaning. Now how the > driver should guess which meaning the user ment when he setted it? > filter or trap? > > That is very confusing. If the flag is the way to do this, let's > introduce another flag, like IFF_TRAPPING indicating that user wants > exactly this. I don't understand how the meaning of promiscuous mode for a networking device has suddenly become ambiguous, when did this start happening?