Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp339063ybz; Tue, 21 Apr 2020 09:59:44 -0700 (PDT) X-Google-Smtp-Source: APiQypIlUxILN6RfGtXrHNF0HfDNIajngid+b45L/SYh3pchcw/KRw28AOOtI9wIQ9KqFcRuc90r X-Received: by 2002:a17:906:54cd:: with SMTP id c13mr21285656ejp.307.1587488383710; Tue, 21 Apr 2020 09:59:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587488383; cv=none; d=google.com; s=arc-20160816; b=wF/VwIR789NLtHEtJ0GsJKiq6DUI6Mh8anZEwT6qZS2Az3bTueul39696c+Q5eKzID fXwx+DESatcjBK1M/5+QIRWdnO10IYzG6h0pKLTeLFEqf4nMEoj3PRYV2IdB1fVLUYRL +uzX8AYkhGABcUPCh2plCv87Kjw04MA4rwYPzGnAAtsaH9roB7sXWaGVoSY5Cnr99XNg 4bdJdifC1XovuY+RN8GtEqqIerJgJAdjTnYq+6DVOTmV2Tnc4KufD/6YCm9qMZueUmmL 6bVwIQuojWzMCVI1cChWENnWuZXwW37453AH0D6gdClCD+cfxy3ryNMPdFYox9CVAqai cJeg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=a4q7ynJ8F9KH7kVbqe3Iu3EL71eV9RhhJw3Rp1O/CzA=; b=GA63NFprIBFh+brGQRDlKC+7nX5SNe+5q4ELLbeYX5tyMeIOYc/7MLBMxGuWs2red3 Umwd8BGYS0gnoFhVJ2hAX9XLXtNOEJKIEY+Y1iVKQf29CxDIAWOjfIPjPquMcMn5t5+5 9fTVDQEOFParY5zoJbEOLOE+AQcTe98CM5TgpMwME0G5vAKsgI6fbEKCT/+udaAle8N+ S6qTd93rO5U+6dHll3f3odxRlvSva7/5bbZ6bNJ3c7t9/5z7jO+MY9/ZF2B/s7cyqBcO F3lmtj4lkaYyXq5nuVTFtkvmtFOWDc4VzzQPVZbANoxHIpGazrj+CUOEsOpxIAbAOtji aglg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=d522WuBx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j9si1039041edn.415.2020.04.21.09.59.20; Tue, 21 Apr 2020 09:59:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=d522WuBx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729202AbgDUQ50 (ORCPT + 99 others); Tue, 21 Apr 2020 12:57:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:57242 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726245AbgDUQyp (ORCPT ); Tue, 21 Apr 2020 12:54:45 -0400 Received: from mail.kernel.org (ip5f5ad4d8.dynamic.kabel-deutschland.de [95.90.212.216]) (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 1F4C82073A; Tue, 21 Apr 2020 16:54:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1587488084; bh=uKk2xVZ7iuzy3Vn3zXrcx8dp/otKv8pCBqbWa51Dqj0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=d522WuBx6JQxLlj38jwiXEqt5yMc25D3cegKjcTEs1D7x7SAhYtm07j6p1zAH/k43 OTqKQfVFq2BM8D2QYTCBJHsv9l8SdNan8gHpX44dQPYaFWKex3IGMbM9ehvkQTmtAh Giu3It7ZwtQBguWREwnynSfl6/67Jlzwv3hcZdAA= Received: from mchehab by mail.kernel.org with local (Exim 4.92.3) (envelope-from ) id 1jQwAU-00CmE1-9n; Tue, 21 Apr 2020 18:54:42 +0200 From: Mauro Carvalho Chehab To: Linux Doc Mailing List Cc: Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, Jonathan Corbet Subject: [PATCH v2 09/29] docs: filesystems: convert automount-support.txt to ReST Date: Tue, 21 Apr 2020 18:54:20 +0200 Message-Id: <46436f998c4a13387d8d6db8d1e7c9a18d02b638.1587487612.git.mchehab+huawei@kernel.org> X-Mailer: git-send-email 2.25.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 - Add a SPDX header; - Add a document title; - Adjust section titles; - Mark literal blocks as such; - Add it to filesystems/index.rst. Signed-off-by: Mauro Carvalho Chehab --- ...ount-support.txt => automount-support.rst} | 23 +++++++++++-------- Documentation/filesystems/index.rst | 2 ++ 2 files changed, 16 insertions(+), 9 deletions(-) rename Documentation/filesystems/{automount-support.txt => automount-support.rst} (92%) diff --git a/Documentation/filesystems/automount-support.txt b/Documentation/filesystems/automount-support.rst similarity index 92% rename from Documentation/filesystems/automount-support.txt rename to Documentation/filesystems/automount-support.rst index 7d9f82607562..430f0b40796b 100644 --- a/Documentation/filesystems/automount-support.txt +++ b/Documentation/filesystems/automount-support.rst @@ -1,3 +1,10 @@ +.. SPDX-License-Identifier: GPL-2.0 + +================= +Automount Support +================= + + Support is available for filesystems that wish to do automounting support (such as kAFS which can be found in fs/afs/ and NFS in fs/nfs/). This facility includes allowing in-kernel mounts to be @@ -5,13 +12,12 @@ performed and mountpoint degradation to be requested. The latter can also be requested by userspace. -====================== -IN-KERNEL AUTOMOUNTING +In-Kernel Automounting ====================== See section "Mount Traps" of Documentation/filesystems/autofs.rst -Then from userspace, you can just do something like: +Then from userspace, you can just do something like:: [root@andromeda root]# mount -t afs \#root.afs. /afs [root@andromeda root]# ls /afs @@ -21,7 +27,7 @@ Then from userspace, you can just do something like: [root@andromeda root]# ls /afs/cambridge/afsdoc/ ChangeLog html LICENSE pdf RELNOTES-1.2.2 -And then if you look in the mountpoint catalogue, you'll see something like: +And then if you look in the mountpoint catalogue, you'll see something like:: [root@andromeda root]# cat /proc/mounts ... @@ -30,8 +36,7 @@ And then if you look in the mountpoint catalogue, you'll see something like: #afsdoc. /afs/cambridge.redhat.com/afsdoc afs rw 0 0 -=========================== -AUTOMATIC MOUNTPOINT EXPIRY +Automatic Mountpoint Expiry =========================== Automatic expiration of mountpoints is easy, provided you've mounted the @@ -43,7 +48,8 @@ To do expiration, you need to follow these steps: hung. (2) When a new mountpoint is created in the ->d_automount method, add - the mnt to the list using mnt_set_expiry() + the mnt to the list using mnt_set_expiry():: + mnt_set_expiry(newmnt, &afs_vfsmounts); (3) When you want mountpoints to be expired, call mark_mounts_for_expiry() @@ -70,8 +76,7 @@ and the copies of those that are on an expiration list will be added to the same expiration list. -======================= -USERSPACE DRIVEN EXPIRY +Userspace Driven Expiry ======================= As an alternative, it is possible for userspace to request expiry of any diff --git a/Documentation/filesystems/index.rst b/Documentation/filesystems/index.rst index 7ed646409030..7fea7c99324e 100644 --- a/Documentation/filesystems/index.rst +++ b/Documentation/filesystems/index.rst @@ -25,6 +25,8 @@ algorithms work. locking directory-locking + automount-support + caching/index porting -- 2.25.2