All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: reiserfs-list@namesys.com
Cc: adilger@clusterfs.com
Subject: Re: [BUG][trivial] atime not set on directory reads
Date: Fri, 14 Jun 2002 09:05:38 +0400	[thread overview]
Message-ID: <20020614090538.A22474@namesys.com> (raw)
In-Reply-To: <20020613213530.GN682@clusterfs.com>

Hello!

   Can you please state kernel version? Bugreports are very useful
   when combined with version of kernel used.

   Anyway problem looking like exactly what you describe was fixed in
   2.4.19-pre3 or thereabout, so can you please also test with
   some recent 2.4.19-pre kernel?

   Thank you for the report.

Bye,
    Oleg
On Thu, Jun 13, 2002 at 03:35:30PM -0600, Andreas Dilger wrote:
> Hello reiserfs folks,
> I'm just in the process of running some POSIX conformance tests on
> Linux (test available at http://www.opengroup.org/testing/lsb-fhs/)
> and reiserfs fails one test where ext2/ext3 are passing.
> 
> The test checks whether atime is updated on a directory if you do a
> directory lookup.  I imagine that it is as simple as adding a call
> UPDATE_ATIME(inode) to the reiserfs directory lookup.  This can, of
> course, be turned off at runtime via the "noatime" mount option (I
> think newer kernels also have a newer "nodiratime").
> 
> Cheers, Andreas
> --
> Andreas Dilger
> http://www-mddsp.enel.ucalgary.ca/People/adilger/
> http://sourceforge.net/projects/ext2resize/
> 

  parent reply	other threads:[~2002-06-14  5:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13 21:35 [BUG][trivial] atime not set on directory reads Andreas Dilger
2002-06-13 22:45 ` Hans Reiser
2002-06-14  5:05 ` Oleg Drokin [this message]
2002-06-14  6:52   ` Andreas Dilger

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=20020614090538.A22474@namesys.com \
    --to=green@namesys.com \
    --cc=adilger@clusterfs.com \
    --cc=reiserfs-list@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.