mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ph. Marek" <philipp.marek@bmlv.gv.at>
To: linux-kernel@vger.kernel.org
Subject: ramfs and directory modification time
Date: Thu, 23 Feb 2006 14:05:03 +0100	[thread overview]
Message-ID: <200602231405.04091.philipp.marek@bmlv.gv.at> (raw)

Hello everybody,

I believe that I found a problem regarding ramfs and directory modification 
times.



Observe:
	$ /tmp# mkdir newdir
	$ /tmp# mount -t ramfs none newdir
	$ /tmp# cd newdir/
	$ /tmp/newdir# mkdir sub
	$ /tmp/newdir# cd sub
	$ /tmp/newdir/sub# ls -la --full-time
	total 0
	drwxr-xr-x 2 root root 0 2006-02-23 14:01:37.573655160 +0100 .
	drwxr-xr-x 3 root root 0 2006-02-23 14:01:33.221316816 +0100 ..
	$ /tmp/newdir/sub# touch a-new-file
	$ /tmp/newdir/sub# ls -la --full-time
	total 0
	drwxr-xr-x 2 root root 0 2006-02-23 14:01:37.573655160 +0100 .
	drwxr-xr-x 3 root root 0 2006-02-23 14:01:33.221316816 +0100 ..
	-rw-r--r-- 1 root root 0 2006-02-23 14:01:48.019067216 +0100 a-new-file

On a tmpfs or other (disk-based) filesystems (ext3) it works correctly.
Is that a design wish, that ramfs is kept as simple as possible?

Nevertheless I believe that should be fixed, as everything that relies on the 
directory mtime won't work on an ramfs.


This is 2.6.26-rc4, btw, on x86.


Please CC me as I'm not subscribed (although I surely will have a look in the 
archives, too).


Regards,

Phil

             reply	other threads:[~2006-02-23 13:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23 13:05 Ph. Marek [this message]
2006-02-24 12:04 ` Andrew Morton
2006-02-26 13:05 Chuck Ebbert

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=200602231405.04091.philipp.marek@bmlv.gv.at \
    --to=philipp.marek@bmlv.gv.at \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®