Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp707615ybz; Wed, 15 Apr 2020 17:10:41 -0700 (PDT) X-Google-Smtp-Source: APiQypIKJ3s30U/tx5lGQbtmfrr3E5AfoDjxXdILBbO9oZ+CAyo4rY7rxSBfB0bmFFMb7hGjONHc X-Received: by 2002:a17:906:1352:: with SMTP id x18mr7699554ejb.138.1586995841531; Wed, 15 Apr 2020 17:10:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586995841; cv=none; d=google.com; s=arc-20160816; b=YxvnAG5QQxX+LSOXk9TsXLYbFl+9LfkdvxKPVemTPMqxl6/cEISe7yh3v4YuErsUWA fT1RiuFcQX7iSzhOryt1ArtOWwFz5oPxzcNxrzYrJNpQgbY0x2pAz3xkaMVDpOVOFwjg URe8f80pBPsM/TomaRBf1PNqrwv9dwdWeRHsBFVgQO88iQg7jdQefP8/GjlSlYhqRKH4 SoRmZ3W2yHoitEAaIvASXtJ/Jvp+OLnF5eX+QMH7IPMho2FIrnAHNiJeLFpV5z4bcsr/ RYTlud/8I4WHXEFlPz9w+TY8L8YZIm+ST8S2Yz0Jz0BRCQcdGjpfFrpmvcR+mIDbwim1 bVYw== 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=yd9NTa4+dDIWRV5DoWziSKboEJpz0XJdI2dUe20tKyg=; b=cjpIGgR/l0NQ7kODWc6hVeYTPpg18ieCGH3odxKoerSqz0IaOPHONFia9ak6gPVuuv jMv3qj5eT2X1F4T3ZIu0oXAJm1ZlXCP4pnw7UZRUN3SvwDBLqECq41bHIsey+P2t38ZI aNGGYVysVpTQsvEfslthtF24jDPkVR4R4aLKirCR4HridV+5TEAWnVAn87NedKTSB0lN krGv2YVxNoOdWkMKsj7xPy7KOCQzLfj2x7XcfpByJD4nxXNZLrdcwak7EenXjjgZM2Pt xuQR5QfTpmZTcNbXfw1aLGqSq9orU76JNffThHrYiGELROhj6q5JyAmSPnqwcoXu1cfL f+kQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=edQAPFix; 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 e2si324899edv.300.2020.04.15.17.10.17; Wed, 15 Apr 2020 17:10:41 -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=edQAPFix; 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 S2636759AbgDOOm5 (ORCPT + 99 others); Wed, 15 Apr 2020 10:42:57 -0400 Received: from mail.kernel.org ([198.145.29.99]:45448 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2394042AbgDOOc6 (ORCPT ); Wed, 15 Apr 2020 10:32:58 -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 161FD2168B; Wed, 15 Apr 2020 14:32:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1586961171; bh=MiIvbtHL1OOpkMTzHlJyILRiWhj8sVsuaKqqb675qZ4=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=edQAPFixUEwxFA1DMbFuOpVW6etWZM5+/X34ROZRkwbwBV6gP5c7JgT5CqUdKdGfQ cvUyKyo1ryZgXTL9JkXTxixoZ4TRx4KHsKZicoP6rfSIQ0f9GfNP15I9fObk6fbRCm IlB16LK+3RHhOmhAZJmzRuDVdD69MJMsrBJ43tjs= Received: from mchehab by mail.kernel.org with local (Exim 4.92.3) (envelope-from ) id 1jOj5t-006kOU-AF; Wed, 15 Apr 2020 16:32:49 +0200 From: Mauro Carvalho Chehab To: Linux Doc Mailing List Cc: Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, Jonathan Corbet Subject: [PATCH 10/34] docs: filesystems: convert automount-support.txt to ReST Date: Wed, 15 Apr 2020 16:32:23 +0200 Message-Id: <677813b103b87ad5dc714d88f3b0e6b9175aa393.1586960617.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 5f4ba0e40e72..fc566c68a458 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