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=-10.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=ham 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 82FD2C433E0 for ; Mon, 15 Jun 2020 06:48:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 5220720739 for ; Mon, 15 Jun 2020 06:48:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592203716; bh=iNcy6BPwUKvaqlgeXJMoimsmOGSQUtlTFOL62ky4fWE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=tI0xDFdwnLXZRtng3IPLNS9tH1OEEJ5l3X1Zs4s0J1TcE4K2wflfGWi3CXR2JCdtj kN6kTQoTZW1UvRp7JWu5KXgct2oXb/y2p+HVgWZxa1iSCa65DP/BGrvSBdzgxvm42+ Tbex2Jie17lRVzorNpzDSTuyaJPWt/z++HlRfITg= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728704AbgFOGse (ORCPT ); Mon, 15 Jun 2020 02:48:34 -0400 Received: from mail.kernel.org ([198.145.29.99]:60088 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728471AbgFOGrO (ORCPT ); Mon, 15 Jun 2020 02:47:14 -0400 Received: from mail.kernel.org (ip5f5ad5c5.dynamic.kabel-deutschland.de [95.90.213.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 2A7E120B1F; Mon, 15 Jun 2020 06:47:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1592203632; bh=iNcy6BPwUKvaqlgeXJMoimsmOGSQUtlTFOL62ky4fWE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=kFLEDZsGQfcO70wO79P2hs7MnqrK4GxsptlpYGBz/WXH5tZB0HgKyNcPe20ITcjM6 Nl9pW1DFTbTXB55k0vJVtwiQ87Jr2yK8aawN/sfNsSJ57DY9S9WRIoyjfp2zi+8WRu Xh/P3rGIbBr2b8pR+MJ8h3BCPB32/1qzs8yqR87Q= Received: from mchehab by mail.kernel.org with local (Exim 4.93) (envelope-from ) id 1jkiti-009nnT-1h; Mon, 15 Jun 2020 08:47:10 +0200 From: Mauro Carvalho Chehab To: Linux Doc Mailing List Cc: Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, Jonathan Corbet , David Howells , Jarkko Sakkinen , keyrings@vger.kernel.org Subject: [PATCH 20/29] docs: watch_queue.rst: supress some Sphinx warnings and move to core-api Date: Mon, 15 Jun 2020 08:46:59 +0200 Message-Id: <6aa020863c158e55387d6282a048f952c31998f6.1592203542.git.mchehab+huawei@kernel.org> X-Mailer: git-send-email 2.26.2 In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sphinx doesn't like multi-line literal blocks with ``foobar``: Documentation/watch_queue.rst:109: WARNING: Inline literal start-string without end-string. Documentation/watch_queue.rst:109: WARNING: Inline emphasis start-string without end-string. Documentation/watch_queue.rst:109: WARNING: Inline emphasis start-string without end-string. Documentation/watch_queue.rst:109: WARNING: Inline emphasis start-string without end-string. Documentation/watch_queue.rst:186: WARNING: Inline literal start-string without end-string. Documentation/watch_queue.rst:186: WARNING: Inline emphasis start-string without end-string. Documentation/watch_queue.rst:185: WARNING: Inline emphasis start-string without end-string. So, let's use the "::" markup instead. While we could do the fix only at the affected lines, let's do the same change along the entire file, in order to preserve the same look and feel at the entire doc. Signed-off-by: Mauro Carvalho Chehab --- Documentation/core-api/index.rst | 1 + Documentation/{ => core-api}/watch_queue.rst | 34 ++++++++++++++------ Documentation/security/keys/core.rst | 2 +- include/linux/watch_queue.h | 2 +- init/Kconfig | 2 +- kernel/watch_queue.c | 2 +- 6 files changed, 30 insertions(+), 13 deletions(-) rename Documentation/{ => core-api}/watch_queue.rst (94%) diff --git a/Documentation/core-api/index.rst b/Documentation/core-api/index.rst index 15ab86112627..ee6957100dec 100644 --- a/Documentation/core-api/index.rst +++ b/Documentation/core-api/index.rst @@ -40,6 +40,7 @@ Library functionality that is used throughout the kernel. generic-radix-tree packing timekeeping + watch_queue errseq Concurrency primitives diff --git a/Documentation/watch_queue.rst b/Documentation/core-api/watch_queue.rst similarity index 94% rename from Documentation/watch_queue.rst rename to Documentation/core-api/watch_queue.rst index 849fad6893ef..ba47adc01239 100644 --- a/Documentation/watch_queue.rst +++ b/Documentation/core-api/watch_queue.rst @@ -103,15 +103,19 @@ watch that specific key). To manage a watch list, the following functions are provided: - * ``void init_watch_list(struct watch_list *wlist, - void (*release_watch)(struct watch *wlist));`` + * :: + + void init_watch_list(struct watch_list *wlist, + void (*release_watch)(struct watch *wlist)); Initialise a watch list. If ``release_watch`` is not NULL, then this indicates a function that should be called when the watch_list object is destroyed to discard any references the watch list holds on the watched object. - * ``void remove_watch_list(struct watch_list *wlist);`` + * :: + + void remove_watch_list(struct watch_list *wlist); This removes all of the watches subscribed to a watch_list and frees them and then destroys the watch_list object itself. @@ -125,14 +129,18 @@ records will be written into. The workings of this are hidden entirely inside of the pipe device driver, but it is necessary to gain a reference to it to set a watch. These can be managed with: - * ``struct watch_queue *get_watch_queue(int fd);`` + * :: + + struct watch_queue *get_watch_queue(int fd);`` Since watch queues are indicated to the kernel by the fd of the pipe that implements the buffer, userspace must hand that fd through a system call. This can be used to look up an opaque pointer to the watch queue from the system call. - * ``void put_watch_queue(struct watch_queue *wqueue);`` + * :: + + void put_watch_queue(struct watch_queue *wqueue); This discards the reference obtained from ``get_watch_queue()``. @@ -168,18 +176,24 @@ different ID are ignored. The following functions are provided to manage watches: - * ``void init_watch(struct watch *watch, struct watch_queue *wqueue);`` + * :: + + void init_watch(struct watch *watch, struct watch_queue *wqueue); Initialise a watch object, setting its pointer to the watch queue, using appropriate barriering to avoid lockdep complaints. - * ``int add_watch_to_object(struct watch *watch, struct watch_list *wlist);`` + * :: + + int add_watch_to_object(struct watch *watch, struct watch_list *wlist); Subscribe a watch to a watch list (notification source). The driver-settable fields in the watch struct must have been set before this is called. - * ``int remove_watch_from_object(struct watch_list *wlist, + * :: + + int remove_watch_from_object(struct watch_list *wlist, struct watch_queue *wqueue, u64 id, false);`` @@ -188,7 +202,9 @@ The following functions are provided to manage watches: (``WATCH_META_REMOVAL_NOTIFICATION``) is sent to the watch queue to indicate that the watch got removed. - * ``int remove_watch_from_object(struct watch_list *wlist, NULL, 0, true);`` + * :: + + int remove_watch_from_object(struct watch_list *wlist, NULL, 0, true); Remove all the watches from a watch list. It is expected that this will be called preparatory to destruction and that the watch list will be diff --git a/Documentation/security/keys/core.rst b/Documentation/security/keys/core.rst index cdc42ccc12e4..e0f1211ca843 100644 --- a/Documentation/security/keys/core.rst +++ b/Documentation/security/keys/core.rst @@ -1046,7 +1046,7 @@ The keyctl syscall functions are: "filter" is either NULL to remove a watch or a filter specification to indicate what events are required from the key. - See Documentation/watch_queue.rst for more information. + See Documentation/core-api/watch_queue.rst for more information. Note that only one watch may be emplaced for any particular { key, queue_fd } combination. diff --git a/include/linux/watch_queue.h b/include/linux/watch_queue.h index 5e08db2adc31..0d8ba47446fa 100644 --- a/include/linux/watch_queue.h +++ b/include/linux/watch_queue.h @@ -4,7 +4,7 @@ * Copyright (C) 2020 Red Hat, Inc. All Rights Reserved. * Written by David Howells (dhowells@redhat.com) * - * See Documentation/watch_queue.rst + * See Documentation/core-api/watch_queue.rst */ #ifndef _LINUX_WATCH_QUEUE_H diff --git a/init/Kconfig b/init/Kconfig index a46aa8f3174d..3327f0eca1a3 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -377,7 +377,7 @@ config WATCH_QUEUE with watches for key/keyring change notifications and device notifications. - See Documentation/watch_queue.rst + See Documentation/core-api/watch_queue.rst config CROSS_MEMORY_ATTACH bool "Enable process_vm_readv/writev syscalls" diff --git a/kernel/watch_queue.c b/kernel/watch_queue.c index f74020f6bd9d..58a4e18390bf 100644 --- a/kernel/watch_queue.c +++ b/kernel/watch_queue.c @@ -4,7 +4,7 @@ * Copyright (C) 2020 Red Hat, Inc. All Rights Reserved. * Written by David Howells (dhowells@redhat.com) * - * See Documentation/watch_queue.rst + * See Documentation/core-api/watch_queue.rst */ #define pr_fmt(fmt) "watchq: " fmt -- 2.26.2