From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Graf Subject: Re: [net-next PATCH v3 00/12] Flow API Date: Thu, 22 Jan 2015 17:58:31 +0000 Message-ID: <20150122175831.GE25797@casper.infradead.org> References: <20150120202404.1741.8658.stgit@nitbit.x32> <20150122125246.GA4486@salvia> <20150122133713.GA25797@casper.infradead.org> <20150122140022.GA5674@salvia> <54C11094.2000807@mojatatu.com> <20150122151316.GB25797@casper.infradead.org> <54C11703.7030702@mojatatu.com> <20150122153727.GC25797@casper.infradead.org> <20150122154840.GC1863@nanopsycho.orion> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jamal Hadi Salim , Pablo Neira Ayuso , John Fastabend , simon.horman@netronome.com, sfeldma@gmail.com, netdev@vger.kernel.org, davem@davemloft.net, gerlitz.or@gmail.com, andy@greyhouse.net, ast@plumgrid.com To: Jiri Pirko Return-path: Received: from casper.infradead.org ([85.118.1.10]:42911 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751609AbbAVR6d (ORCPT ); Thu, 22 Jan 2015 12:58:33 -0500 Content-Disposition: inline In-Reply-To: <20150122154840.GC1863@nanopsycho.orion> Sender: netdev-owner@vger.kernel.org List-ID: On 01/22/15 at 04:48pm, Jiri Pirko wrote: > Thu, Jan 22, 2015 at 04:37:27PM CET, tgraf@suug.ch wrote: > >On 01/22/15 at 10:28am, Jamal Hadi Salim wrote: > >> On 01/22/15 10:13, Thomas Graf wrote: > >> > >> >I don't follow this. John's proposal allows to decide on a case by > >> >case basis what we want to export. Just like with ethtool or > >> >RTNETLINK. There is no direct access to hardware. A user can only > >> >configure what is being exposed by the kernel. > >> > > >> > >> So if i am a vendor with my own driver, I can expose whatever i want. > > > >No. We will reject any driver change attempting to do so on this > >list. > > That is not 100%, on contrary. If the infrastructure would be made to > explicitly disallow that kind of behaviour, it would be much safer. I'm very much in favour of that. Ideas?