From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E1758C433DF for ; Fri, 24 Jul 2020 07:25:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id BC2B12065E for ; Fri, 24 Jul 2020 07:25:20 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="fPQU5YAO" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726727AbgGXHZU (ORCPT ); Fri, 24 Jul 2020 03:25:20 -0400 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:37055 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726666AbgGXHZT (ORCPT ); Fri, 24 Jul 2020 03:25:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1595575518; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=fuErLOqr2wiHuSm1n+glJqJxYG3jv4lWg3NgZEQOlPE=; b=fPQU5YAOHeVpb/XBWql+enb3J1xB5CBDy8DczdAQ4HtDXLrq8hROvvEqGYJd8krSqb0GtK 6Bisi/7F3+nHql9oAOKzUp6l1c61KzJQ03Vxaod6kWTUW2DuihfXEcd+huwbjRLhTEtY1F EubOu984psNZZTE6mSmraAEp0snG5Mk= Received: from mail-wr1-f72.google.com (mail-wr1-f72.google.com [209.85.221.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-400-1iPoeSo6PKq_YOqG684fug-1; Fri, 24 Jul 2020 03:25:16 -0400 X-MC-Unique: 1iPoeSo6PKq_YOqG684fug-1 Received: by mail-wr1-f72.google.com with SMTP id s23so1718357wrb.12 for ; Fri, 24 Jul 2020 00:25:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=fuErLOqr2wiHuSm1n+glJqJxYG3jv4lWg3NgZEQOlPE=; b=AMMXtMxy9l9IvUZF05lr2EnGeHrWbV4nPc+dHfJjCXtfNeIXJr8JGmXiZJX2Ofcefr fbbEoZUF9LRLVnJarXe/L3TbnLMn8M8oOkzGxkbBoMf9AZEiRDVNMpogKeba58W4lOCy rorLraewBdmpRTe1Cht7c2BAYd7lJWkfM58gVQhJrR/KYZ5/rLxkDImSAAnP/6vGIV9U rpTt1fk0RlK4dyc5Rq9tdL2D430DX9mazBxGclqAXhMwBM7SBqFH8qbzZ8Ho2RrtgTi+ wazVm4eyKkLl+Dsm7isO2Mdi6sA362quFLl9uyFggYcIG1u5iz8oagxrEK8DpdE6S9Lt 015w== X-Gm-Message-State: AOAM530NH5tWYGn1v9nTuG4vh1NGcdQx3heLX+TKoBBfdHjBQSDgz7wg nrh8JrbzqZvQhxK80zmn1Je6EzmBreUcxYyfxyDWor01+iKhmWFREhgCz4XX3xX/HCocyg1Yg0C 9/8S3VQrYw0AG9NIIqSA= X-Received: by 2002:adf:bb52:: with SMTP id x18mr7081709wrg.325.1595575515196; Fri, 24 Jul 2020 00:25:15 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwjC5TNOMsbWloWKiM1fPLp95PjAuhLTb70ke99fpxMRmPpCdyrTQ/Uxi1NsfB0ImOP4RPRkA== X-Received: by 2002:adf:bb52:: with SMTP id x18mr7081693wrg.325.1595575514967; Fri, 24 Jul 2020 00:25:14 -0700 (PDT) Received: from steredhat.lan ([5.171.199.112]) by smtp.gmail.com with ESMTPSA id p25sm5864195wmg.39.2020.07.24.00.25.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 24 Jul 2020 00:25:14 -0700 (PDT) Date: Fri, 24 Jul 2020 09:25:09 +0200 From: Stefano Garzarella To: Colin Walters Cc: Andy Lutomirski , Jens Axboe , Christoph Hellwig , Kees Cook , Pavel Begunkov , Miklos Szeredi , Matthew Wilcox , Jann Horn , Christian Brauner , strace-devel@lists.strace.io, io-uring@vger.kernel.org, Linux API , Linux FS Devel , LKML , Michael Kerrisk , Stefan Hajnoczi Subject: Re: strace of io_uring events? Message-ID: <20200724072509.sgqlbuocpo2peian@steredhat.lan> References: <7c09f6af-653f-db3f-2378-02dca2bc07f7@gmail.com> <48cc7eea-5b28-a584-a66c-4eed3fac5e76@gmail.com> <202007151511.2AA7718@keescook> <20200716131404.bnzsaarooumrp3kx@steredhat> <202007160751.ED56C55@keescook> <20200717080157.ezxapv7pscbqykhl@steredhat.lan> <20200721155848.32xtze5ntvcmjv63@steredhat> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: io-uring-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org On Thu, Jul 23, 2020 at 09:37:40AM -0400, Colin Walters wrote: > On Tue, Jul 21, 2020, at 11:58 AM, Stefano Garzarella wrote: > > > my use case concerns virtualization. The idea, that I described in the > > proposal of io-uring restrictions [1], is to share io_uring CQ and SQ queues > > with a guest VM for block operations. > > Virtualization being a strong security barrier is in eternal conflict > with maximizing performance. All of these "let's add a special > guest/host channel" are high risk areas. > > And this effort in particular - is it *really* worth it to expose a > brand new, fast moving Linux kernel interface (that probably hasn't > been fuzzed as much as it needs to be) to virtual machines? > It is an experiment to explore the potential of io_uring. In addition the restrictions can also be useful for other use case, for example if a process wants to allow another process to use io_uring, but only allowing a subset of operations. > People who want maximum performance at the cost of a bit of security > already have the choice to use Linux containers, where they can use > io_uring natively. > Thanks, Stefano