linux-kernel - Re: [PATCH] virtio_mmio: expose header to userspace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20170113152618-mutt-send-email-mst@kernel.org>
Date:   Fri, 13 Jan 2017 15:31:14 +0200
From:   "Michael S. Tsirkin" <mst@...hat.com>
To:     Christoph Hellwig <hch@...radead.org>
Cc:     linux-kernel@...r.kernel.org, Jason Wang <jasowang@...hat.com>,
        virtualization@...ts.linux-foundation.org
Subject: Re: [PATCH] virtio_mmio: expose header to userspace

On Thu, Jan 12, 2017 at 11:58:22PM -0800, Christoph Hellwig wrote:
> On Thu, Jan 12, 2017 at 11:37:22PM +0200, Michael S. Tsirkin wrote:
> > It's handy for userspace emulators like QEMU.
> 
> But it's not actually a userspace API - it's an on the write protocol.

We do this for all other virtio transports, mmio shouldn't be
any different.

> so: NAK.

We'll have to agree to disagree on this one. It's the interface
beween linux and the hypervisor. It isn't any less stable
than the one to userspace, for better or worse kvm
(ab)uses uapi for that. Compare also to include/uapi/linux/kvm_para.h
etc.

-- 
MST