From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 292DC7E23 for ; Thu, 1 Oct 2015 17:40:54 +0200 (CEST) Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (Postfix) with ESMTPS id 64BD98E69C; Thu, 1 Oct 2015 15:40:53 +0000 (UTC) Received: from redhat.com (ovpn-116-83.ams2.redhat.com [10.36.116.83]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with SMTP id t91FenYX014799; Thu, 1 Oct 2015 11:40:51 -0400 Date: Thu, 1 Oct 2015 18:40:49 +0300 From: "Michael S. Tsirkin" To: Avi Kivity Message-ID: <20151001154049.GB25009@redhat.com> References: <20151001124211-mutt-send-email-mst@redhat.com> <560D0413.5080401@scylladb.com> <20151001131754-mutt-send-email-mst@redhat.com> <560D0FE2.7010905@scylladb.com> <20151001135054-mutt-send-email-mst@redhat.com> <560D1705.30300@scylladb.com> <20151001142640-mutt-send-email-mst@redhat.com> <560D19C3.4060206@scylladb.com> <20151001151154.GA24549@redhat.com> <560D4F05.5040105@scylladb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <560D4F05.5040105@scylladb.com> X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Having troubles binding an SR-IOV VF to uio_pci_generic on Amazon instance X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Oct 2015 15:40:54 -0000 On Thu, Oct 01, 2015 at 06:19:33PM +0300, Avi Kivity wrote: > On 10/01/2015 06:11 PM, Michael S. Tsirkin wrote: > >On Thu, Oct 01, 2015 at 02:32:19PM +0300, Avi Kivity wrote: > >>> We already agreed this kernel > >>>is going to be tainted, and unsupportable. > >>Yes. So your only motivation in rejecting the patch is to get the author to > >>write the ring translation patch and port it to all relevant drivers > >>instead? > >Not only that. > > > >To make sure users are aware they are doing insecure > >things when using software poking at device BARs in sysfs. > > I don't think you need to worry about that. People who program DMA are > aware of the damage is can cause. People just install software and run it. They don't program DMA. And I notice that no software (ab)using this seems to come with documentation explaining the implications. > If you want to be extra sure, have uio > taint the kernel when bus mastering is enabled. People don't notice kernel is tainted. Denying module load will make them notice. -- MST