From: Herbert Poetzl <herbert@13thfloor.at>
To: Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Cc: raven@themaw.net, autofs@linux.kernel.org
Subject: Re: [Patch 2/6] Bind Mount Extensions 0.06
Date: Thu, 24 Feb 2005 22:17:27 +0100 [thread overview]
Message-ID: <20050224211727.GD4981@mail.13thfloor.at> (raw)
In-Reply-To: <20050223230105.GD21383@infradead.org>
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?
not yet!
(cc-ed to automounter maintainer and list)
thanks,
Herbert
> -
> 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/
next prev parent reply other threads:[~2005-02-24 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 12:11 [Patch 2/6] Bind Mount Extensions 0.06 Herbert Poetzl
2005-02-23 23:01 ` Christoph Hellwig
2005-02-24 21:17 ` Herbert Poetzl [this message]
2005-02-25 13:15 ` raven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050224211727.GD4981@mail.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=akpm@osdl.org \
--cc=autofs@linux.kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox