From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754965AbbJHIwj (ORCPT ); Thu, 8 Oct 2015 04:52:39 -0400 Received: from mail-wi0-f179.google.com ([209.85.212.179]:37148 "EHLO mail-wi0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754932AbbJHIwg (ORCPT ); Thu, 8 Oct 2015 04:52:36 -0400 Date: Thu, 8 Oct 2015 11:52:32 +0300 From: Gleb Natapov To: "Michael S. Tsirkin" Cc: Avi Kivity , Alex Williamson , Vlad Zolotarov , Greg KH , linux-kernel@vger.kernel.org, hjk@hansjkoch.de, corbet@lwn.net, bruce.richardson@intel.com, avi@cloudius-systems.com, gleb@cloudius-systems.com, stephen@networkplumber.org, alexander.duyck@gmail.com Subject: Re: [PATCH v3 2/3] uio_pci_generic: add MSI/MSI-X support Message-ID: <20151008085232.GG11716@scylladb.com> References: <5613DE26.1090202@cloudius-systems.com> <20151006174648-mutt-send-email-mst@redhat.com> <5613E75E.1040002@scylladb.com> <1444157480.4059.67.camel@redhat.com> <5614C11B.6090601@scylladb.com> <1444235464.4059.169.camel@redhat.com> <56154AB4.1050509@scylladb.com> <20151007230553-mutt-send-email-mst@redhat.com> <56160039.4090901@scylladb.com> <20151008104212-mutt-send-email-mst@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151008104212-mutt-send-email-mst@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 08, 2015 at 11:32:50AM +0300, Michael S. Tsirkin wrote: > On Thu, Oct 08, 2015 at 08:33:45AM +0300, Avi Kivity wrote: > > On 08/10/15 00:05, Michael S. Tsirkin wrote: > > >On Wed, Oct 07, 2015 at 07:39:16PM +0300, Avi Kivity wrote: > > >>That's what I thought as well, but apparently adding msix support to the > > >>already insecure uio drivers is even worse. > > >I'm glad you finally agree what these drivers are doing is insecure. > > > > > >And basically kernel cares about security, no one wants to maintain insecure stuff. > > > > > >So you guys should think harder whether this code makes any sense upstream. > > > > You simply ignore everything I write, cherry-picking the word "insecure" as > > if it makes your point. That is very frustrating. > > And I'm sorry about the frustration. I didn't intend to twist your > words. It's just that I had to spend literally hours trying to explain > that security matters in kernel, and all I was getting back was a > summary "there's no security issue because there are other way to > corrupt memory". > That's not the (only) answer that you were given. The answers that you constantly ignore is that the patch in question does not add any new ways to corrupt memory which are not possible using _upstream_ uio_pci_generic device, so the fact that uio_pci_generic can corrupt memory cannot be used as a reason to not apply patches that do not corrupt any memory. You seams to be constantly arguing that uio_pci_generic is not suitable for upstream. -- Gleb.