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=-19.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_GIT 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 76ACFC433E9 for ; Mon, 29 Mar 2021 22:19:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 58F89619A0 for ; Mon, 29 Mar 2021 22:19:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231814AbhC2WTK (ORCPT ); Mon, 29 Mar 2021 18:19:10 -0400 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:28107 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231623AbhC2WSr (ORCPT ); Mon, 29 Mar 2021 18:18:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1617056326; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WUaW949Sngo6yyC4xTwj+erWp36FebBIUp15Ep+mJGo=; b=NfoOOIhn4OfijpNMN6Hssai+l6yc+1NCa65dumqWFMsKgwnYN5oO9mrcgsc3WccMbWK0po tYKkP0Q+WJl1XViJJ/3l+efz1oODoYU785o/7suuLYLV9JPpSy5IiOA2sgaaN+HrRzaVr/ Hy4dmq76HzEjyyu1wAZaVj7aji8mQhE= Received: from mail-qk1-f197.google.com (mail-qk1-f197.google.com [209.85.222.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-508-7rUhujMtNYGJjxXY-QvJyQ-1; Mon, 29 Mar 2021 18:18:44 -0400 X-MC-Unique: 7rUhujMtNYGJjxXY-QvJyQ-1 Received: by mail-qk1-f197.google.com with SMTP id v136so13214758qkb.9 for ; Mon, 29 Mar 2021 15:18:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=WUaW949Sngo6yyC4xTwj+erWp36FebBIUp15Ep+mJGo=; b=PjP0wfq/WS2FnpMypdQHvtQegtBgsZjQOgl6pnw5+HvVlynDd9+Lf96zeGKznDm9bS YC7ySuQF6gNB+qFukzMOoEuSLGZI3MjfngdW9kDolCQpZPa2wFSV1El8XFhfoYtaARzX +4iWbK9jmNd3E4G81lq09AamhHvSdp1uvVYhDLm6b82ikmppuVpVZNt8wI/CbStRX0WP mRwNNVd/JujDwnwll3jj3HE0Xge1BUub+OvjGyxry98OlqAvkOkpawm+ksfNBlZuzXvF vKqA+IxFjjcj0pIFBPOx4LGt0F1pOuzE+72Z76OeZIH/5ULKZBZ7kAl9RQiQjwfJnvNN jpRw== X-Gm-Message-State: AOAM5315UTCn6sFkdLWSrjdyRVLxYlk8w1hvsRzCMKazVqreKkaVtsVy 7PtOgAjiO7M6M9onFGfpeFcdoyLrIVUMe1uoQnzW6XWHj4XQDs/+o+mbbq5RvRTbwa6Ri966iGv sYa4zx4bSS+4o43cH60Q+pDKq X-Received: by 2002:ac8:1009:: with SMTP id z9mr24461427qti.128.1617056323589; Mon, 29 Mar 2021 15:18:43 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyxdKP9FUZ/PE3P0cEW+pqhOmx0ng44ycgosjq2R17bSMGFeko3E8KREiwoyB8K2f+jnIt6NQ== X-Received: by 2002:ac8:1009:: with SMTP id z9mr24461400qti.128.1617056323323; Mon, 29 Mar 2021 15:18:43 -0700 (PDT) Received: from xz-x1.redhat.com (bras-base-toroon474qw-grc-82-174-91-135-175.dsl.bell.ca. [174.91.135.175]) by smtp.gmail.com with ESMTPSA id i17sm12255215qtr.33.2021.03.29.15.18.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 29 Mar 2021 15:18:42 -0700 (PDT) From: Peter Xu To: linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-man@vger.kernel.org Cc: Axel Rasmussen , peterx@redhat.com, Nadav Amit , Mike Rapoport , Alejandro Colomar , Andrea Arcangeli , Michael Kerrisk , Andrew Morton Subject: [PATCH v5 4/4] ioctl_userfaultfd.2: Add write-protect mode docs Date: Mon, 29 Mar 2021 18:18:33 -0400 Message-Id: <20210329221833.517923-5-peterx@redhat.com> X-Mailer: git-send-email 2.26.2 In-Reply-To: <20210329221833.517923-1-peterx@redhat.com> References: <20210329221833.517923-1-peterx@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Userfaultfd write-protect mode is supported starting from Linux 5.7. Acked-by: Mike Rapoport Signed-off-by: Peter Xu --- man2/ioctl_userfaultfd.2 | 84 ++++++++++++++++++++++++++++++++++++++-- 1 file changed, 81 insertions(+), 3 deletions(-) diff --git a/man2/ioctl_userfaultfd.2 b/man2/ioctl_userfaultfd.2 index d4a8375b8..ca533a383 100644 --- a/man2/ioctl_userfaultfd.2 +++ b/man2/ioctl_userfaultfd.2 @@ -234,6 +234,11 @@ operation is supported. The .B UFFDIO_UNREGISTER operation is supported. +.TP +.B 1 << _UFFDIO_WRITEPROTECT +The +.B UFFDIO_WRITEPROTECT +operation is supported. .PP This .BR ioctl (2) @@ -322,9 +327,6 @@ Track page faults on missing pages. .B UFFDIO_REGISTER_MODE_WP Track page faults on write-protected pages. .PP -Currently, the only supported mode is -.BR UFFDIO_REGISTER_MODE_MISSING . -.PP If the operation is successful, the kernel modifies the .I ioctls bit-mask field to indicate which @@ -443,6 +445,16 @@ operation: .TP .B UFFDIO_COPY_MODE_DONTWAKE Do not wake up the thread that waits for page-fault resolution +.TP +.B UFFDIO_COPY_MODE_WP +Copy the page with read-only permission. +This allows the user to trap the next write to the page, +which will block and generate another write-protect userfault message. +This is only used when both +.B UFFDIO_REGISTER_MODE_MISSING +and +.B UFFDIO_REGISTER_MODE_WP +modes are enabled for the registered range. .PP The .I copy @@ -654,6 +666,72 @@ field of the structure was not a multiple of the system page size; or .I len was zero; or the specified range was otherwise invalid. +.SS UFFDIO_WRITEPROTECT (Since Linux 5.7) +Write-protect or write-unprotect an userfaultfd registered memory range +registered with mode +.BR UFFDIO_REGISTER_MODE_WP . +.PP +The +.I argp +argument is a pointer to a +.I uffdio_range +structure as shown below: +.PP +.in +4n +.EX +struct uffdio_writeprotect { + struct uffdio_range range; /* Range to change write permission */ + __u64 mode; /* Mode to change write permission */ +}; +.EE +.in +There're two mode bits that are supported in this structure: +.TP +.B UFFDIO_WRITEPROTECT_MODE_WP +When this mode bit is set, the ioctl will be a write-protect operation upon the +memory range specified by +.IR range . +Otherwise it'll be a write-unprotect operation upon the specified range, +which can be used to resolve an userfaultfd write-protect page fault. +.TP +.B UFFDIO_WRITEPROTECT_MODE_DONTWAKE +When this mode bit is set, +do not wake up any thread that waits for page-fault resolution after the operation. +This could only be specified if +.B UFFDIO_WRITEPROTECT_MODE_WP +is not specified. +.PP +This +.BR ioctl (2) +operation returns 0 on success. +On error, \-1 is returned and +.I errno +is set to indicate the error. +Possible errors include: +.TP +.B EINVAL +The +.I start +or the +.I len +field of the +.I ufdio_range +structure was not a multiple of the system page size; or +.I len +was zero; or the specified range was otherwise invalid. +.TP +.B EAGAIN +The process was interrupted; retry this call. +.TP +.B ENOENT +The range specified in +.I range +is not valid. +For example, the virtual address does not exist, +or not registered with userfaultfd write-protect mode. +.TP +.B EFAULT +Encountered a generic fault during processing. .SH RETURN VALUE See descriptions of the individual operations, above. .SH ERRORS -- 2.26.2