Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262691AbVBYNSe (ORCPT ); Fri, 25 Feb 2005 08:18:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262693AbVBYNSe (ORCPT ); Fri, 25 Feb 2005 08:18:34 -0500 Received: from wombat.indigo.net.au ([202.0.185.19]:12550 "EHLO wombat.indigo.net.au") by vger.kernel.org with ESMTP id S262691AbVBYNRg (ORCPT ); Fri, 25 Feb 2005 08:17:36 -0500 Date: Fri, 25 Feb 2005 21:15:12 +0800 (WST) From: raven@themaw.net To: Herbert Poetzl cc: Christoph Hellwig , Andrew Morton , Al Viro , Linux Kernel ML , autofs@linux.kernel.org Subject: Re: [Patch 2/6] Bind Mount Extensions 0.06 In-Reply-To: <20050224211727.GD4981@mail.13thfloor.at> Message-ID: References: <20050222121129.GC3682@mail.13thfloor.at> <20050223230105.GD21383@infradead.org> <20050224211727.GD4981@mail.13thfloor.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-100.6, required 8, EMAIL_ATTRIBUTION, IN_REP_TO, NO_REAL_NAME, QUOTED_EMAIL_TEXT, RCVD_IN_ORBS, RCVD_IN_OSIRUSOFT_COM, REFERENCES, REPLY_WITH_QUOTES, USER_AGENT_PINE, USER_IN_WHITELIST) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1444 Lines: 43 On Thu, 24 Feb 2005, Herbert Poetzl wrote: > On Wed, Feb 23, 2005 at 11:01:05PM +0000, Christoph Hellwig wrote: >> On Tue, Feb 22, 2005 at 01:11:29PM +0100, Herbert Poetzl wrote: >>> >>> >>> ; >>> ; Bind Mount Extensions >>> ; >>> ; This part adds the required checks for touch_atime() to allow >>> ; for vfsmount based NOATIME and NODIRATIME >>> ; autofs4 update_atime is the only exception (ignored on purpose) >> >> and that purpose is? > > this is based on a statement from Al Viro: > > | autofs4 use - AFAICS there we want atime updated unconditionally, > | so calling update_atime() (update atime after checking > | noatime/nodiratime/readonly flags) is wrong. > > agreed, maybe a proper fix would be better ... > >> Did you discuss this with the autofs maintainers? I've had a look at the patch and I can't see any problem. autofs4 doesn't use the inode atime for expire purposes but does update it in sync with its dentry info struct field that is used for this purpose. So AFAICS the atime is an external view of expire status, but only when updated within the autofs4 module VFS callbacks. I haven't yet looked at the v3 (autofs) module. I'll get back if I see an issue there. Ian - 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/