From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 6/28] VFS: Make expiry recursive Date: Mon, 25 Oct 2004 16:04:16 +0100 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20041025150416.GA1603@infradead.org> References: <10987152612887@sun.com> <1098715291724@sun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, raven@themaw.net Return-path: Received: from phoenix.infradead.org ([81.187.226.98]:56588 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S261918AbUJYPEQ (ORCPT ); Mon, 25 Oct 2004 11:04:16 -0400 To: Mike Waychison Content-Disposition: inline In-Reply-To: <1098715291724@sun.com> List-Id: linux-fsdevel.vger.kernel.org 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)