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=-9.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 0AFF2C433DF for ; Thu, 27 Aug 2020 14:50:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D9DC22054F for ; Thu, 27 Aug 2020 14:50:58 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="hIDHGbPD" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728134AbgH0Out (ORCPT ); Thu, 27 Aug 2020 10:50:49 -0400 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:34747 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728018AbgH0NlP (ORCPT ); Thu, 27 Aug 2020 09:41:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1598535659; 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: content-transfer-encoding:content-transfer-encoding; bh=3kTaC7Koe/EnnFofVOMX9+NxqY3+OHKyUa+e0ym9rLY=; b=hIDHGbPDclp2byrsRLV9zndZpiBRTC8BmhU0ALcA9Sh3Gze7sS6e0VzWV+L8wgmHElHvWx pugsZ6Sdb9+6J0qaibNlNh4fTP/vXGo/JuhI1RhlAtLvWIY3+p8CLC3nKmb7/04T3hB7VD PqKTpxcgm6AOBSCctBe+y/hfAtMSZKc= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-108-1b2BLQODPwSPJVSK4YyNIg-1; Thu, 27 Aug 2020 09:40:55 -0400 X-MC-Unique: 1b2BLQODPwSPJVSK4YyNIg-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 2FDA318A2251; Thu, 27 Aug 2020 13:40:53 +0000 (UTC) Received: from steredhat.redhat.com (ovpn-113-96.ams2.redhat.com [10.36.113.96]) by smtp.corp.redhat.com (Postfix) with ESMTP id C5AD17D4E4; Thu, 27 Aug 2020 13:40:45 +0000 (UTC) From: Stefano Garzarella To: Jens Axboe Cc: Aleksa Sarai , Kernel Hardening , Jann Horn , io-uring@vger.kernel.org, Christian Brauner , linux-fsdevel@vger.kernel.org, Alexander Viro , Stefan Hajnoczi , linux-kernel@vger.kernel.org, Sargun Dhillon , Kees Cook , Jeff Moyer Subject: [PATCH v5 0/3] io_uring: add restrictions to support untrusted applications and guests Date: Thu, 27 Aug 2020 15:40:41 +0200 Message-Id: <20200827134044.82821-1-sgarzare@redhat.com> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Sender: io-uring-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org v5: - explicitly assigned enum values [Kees] - replaced kmalloc/copy_from_user with memdup_user [kernel test robot] - added Kees' R-b tags v4: https://lore.kernel.org/io-uring/20200813153254.93731-1-sgarzare@redhat.com/ v3: https://lore.kernel.org/io-uring/20200728160101.48554-1-sgarzare@redhat.com/ RFC v2: https://lore.kernel.org/io-uring/20200716124833.93667-1-sgarzare@redhat.com RFC v1: https://lore.kernel.org/io-uring/20200710141945.129329-1-sgarzare@redhat.com Following the proposal that I send about restrictions [1], I wrote this series to add restrictions in io_uring. I also wrote helpers in liburing and a test case (test/register-restrictions.c) available in this repository: https://github.com/stefano-garzarella/liburing (branch: io_uring_restrictions) Just to recap the proposal, the idea is to add some restrictions to the operations (sqe opcode and flags, register opcode) to safely allow untrusted applications or guests to use io_uring queues. The first patch changes io_uring_register(2) opcodes into an enumeration to keep track of the last opcode available. The second patch adds IOURING_REGISTER_RESTRICTIONS opcode and the code to handle restrictions. The third patch adds IORING_SETUP_R_DISABLED flag to start the rings disabled, allowing the user to register restrictions, buffers, files, before to start processing SQEs. Comments and suggestions are very welcome. Thank you in advance, Stefano [1] https://lore.kernel.org/io-uring/20200609142406.upuwpfmgqjeji4lc@steredhat/ Stefano Garzarella (3): io_uring: use an enumeration for io_uring_register(2) opcodes io_uring: add IOURING_REGISTER_RESTRICTIONS opcode io_uring: allow disabling rings during the creation fs/io_uring.c | 155 ++++++++++++++++++++++++++++++++-- include/uapi/linux/io_uring.h | 60 ++++++++++--- 2 files changed, 198 insertions(+), 17 deletions(-) -- 2.26.2