Date: Mon, 25 Oct 2004 16:04:16 +0100
From: Christoph Hellwig <hch@infradead.org>
To: Mike Waychison <michael.waychison@sun.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
       raven@themaw.net
Subject: Re: [PATCH 6/28] VFS: Make expiry recursive
Message-ID: <20041025150416.GA1603@infradead.org>
Mail-Followup-To: Christoph Hellwig <hch@infradead.org>,
	Mike Waychison <michael.waychison@sun.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	raven@themaw.net
References: <10987152612887@sun.com> <1098715291724@sun.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1098715291724@sun.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1124
Lines: 24

On Mon, Oct 25, 2004 at 10:41:31AM -0400, Mike Waychison wrote:
> This patch allows for tagging of vfsmounts as being part of a sub-tree
> expiry.  It introduces a new vfsmount flag, MNT_CHILDEXPIRE which is used to
> let the system know that the given mountpoint expires with its parent.  This
> is a recursive definition.
> 
> mnt_expiry, the call used to specify that a mount should expire, now takes an
> int described as follows:
>    -  0  -   The mountpoint should not expire (default)
>    - >0  -   The value is used to specify the amount of idle time before the
>              given mountpoint expires.
>    - <0  -   The mountpoint must expire with it's immediate parent.  (parent
>              must be set to expire, or must be itself be marked to expire
>              along with _its_ parent.

so add some constant for this, ala

#define MNT_EXPIRE_RECURSIVE	(-1)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/