From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: virtio-comment-return-656-cohuck=redhat.com@lists.oasis-open.org Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 857DB985B92 for ; Mon, 25 Feb 2019 23:08:32 +0000 (UTC) MIME-Version: 1.0 References: <20190225083700-mutt-send-email-mst@kernel.org> <20190225151735-mutt-send-email-mst@kernel.org> In-Reply-To: <20190225151735-mutt-send-email-mst@kernel.org> From: Roman Kiryanov Date: Mon, 25 Feb 2019 15:08:19 -0800 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: [virtio-comment] Re: RFC: virtio-hostmem (+ Continuation of discussion from [virtio-dev] Memory sharing device) To: "Michael S. Tsirkin" Cc: Frank Yang , virtio-comment@lists.oasis-open.org, Cornelia Huck , Gerd Hoffmann , Stefan Hajnoczi , "Dr. David Alan Gilbert" List-ID: Michael, thank you for your comments. > I'm not sure how does above answer the comment. Sorry for leaving this unclear, our guest driver tells the device guest's page size and then we do aligning-unaligning. > To try and put things in your terms, if you try to map a range of memory > you get access to a page that can be bigger than the range you asked > for. This is correct. > It can cause two ranges to violate a security boundary, cause > information leaks, etc. Could you please correct me if I am wrong. If I ask glMapBufferRange (without hosts and guests) for a 1K buffer with 4K pages, I will have access to other 3K. If a driver decides to put sensitive bits there - will this be the same situation? We assume pages are not shared between processes. If this assumption does not work then it is hard to share arbitrary pointers. Regards, Roman. This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: virtio-comment-subscribe@lists.oasis-open.org Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org List help: virtio-comment-help@lists.oasis-open.org List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/