linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Al Viro <viro@ftp.linux.org.uk>
Subject: Re: ramfs and directory modification time
Date: Sun, 26 Feb 2006 08:05:06 -0500	[thread overview]
Message-ID: <200602260807_MC3-1-B952-1BBE@compuserve.com> (raw)

In-Reply-To: <20060224040400.2f093523.akpm@osdl.org>

On Fri, 24 Feb 2006 at 04:04:00 -0800, Andrew Morton wrote:

> --- devel/fs/ramfs/inode.c~ramfs-update-dir-mtime-and-ctime   2006-02-24 03:53:46.000000000 -0800
> +++ devel-akpm/fs/ramfs/inode.c       2006-02-24 03:54:29.000000000 -0800
> @@ -27,6 +27,7 @@
>  #include <linux/fs.h>
>  #include <linux/pagemap.h>
>  #include <linux/highmem.h>
> +#include <linux/time.h>
>  #include <linux/init.h>
>  #include <linux/string.h>
>  #include <linux/smp_lock.h>
> @@ -104,6 +105,7 @@ ramfs_mknod(struct inode *dir, struct de
>               d_instantiate(dentry, inode);
>               dget(dentry);   /* Extra count - pin the dentry in core */
>               error = 0;
> +             dir->i_mtime = dir->i_ctime = CURRENT_TIME_SEC;
>       }
>       return error;
>  }


 Shouldn't that be CURRENT_TIME?

[me@tu ramfs]$ grep -i current_time *
inode.c:                inode->i_atime = inode->i_mtime = inode->i_ctime = CURRENT_TIME;


-- 
Chuck
"Equations are the Devil's sentences."  --Stephen Colbert


             reply	other threads:[~2006-02-26 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-26 13:05 Chuck Ebbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-23 13:05 ramfs and directory modification time Ph. Marek
2006-02-24 12:04 ` Andrew Morton

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=200602260807_MC3-1-B952-1BBE@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.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;
as well as URLs for NNTP newsgroup(s).