mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Taesoo Kim <tsgatesv@gmail.com>
Cc: jack@suse.cz, linux-kernel@vger.kernel.org, taesoo@gatech.edu,
	changwoo@gatech.edu, sanidhya@gatech.edu, blee@gatech.edu,
	csong84@gatech.edu
Subject: Re: [PATCH 1/1] udf: update ctime and mtime of new_dir
Date: Wed, 1 Apr 2015 14:29:43 +0200	[thread overview]
Message-ID: <20150401122943.GJ26339@quack.suse.cz> (raw)
In-Reply-To: <1427230045-11457-1-git-send-email-tsgatesv@gmail.com>

On Tue 24-03-15 16:47:25, Taesoo Kim wrote:
> Upon successful rename(), update ctime and mtime of new_dir
> as posix specifies.
> 
> Signed-off-by: Taesoo Kim <tsgatesv@gmail.com>
  Thanks for spotting the problem! But you apparently didn't test the patch
because it doesn't fix the problem - you've placed the timestamp update
into a wrong branch. Please test the patches before you send them.

I've fixed the problem together with similar issues during file creation,
link, etc.

								Honza

> ---
>  fs/udf/namei.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/fs/udf/namei.c b/fs/udf/namei.c
> index 33b246b..eca1955 100644
> --- a/fs/udf/namei.c
> +++ b/fs/udf/namei.c
> @@ -1144,6 +1144,8 @@ static int udf_rename(struct inode *old_dir, struct dentry *old_dentry,
>  			inode_dec_link_count(new_inode);
>  		else {
>  			inc_nlink(new_dir);
> +			new_dir->i_ctime = new_dir->i_mtime
> +				= current_fs_time(new_dir->i_sb);
>  			mark_inode_dirty(new_dir);
>  		}
>  	}
> -- 
> 2.3.3
> 
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

      reply	other threads:[~2015-04-01 12:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 20:47 Taesoo Kim
2015-04-01 12:29 ` Jan Kara [this message]

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=20150401122943.GJ26339@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=blee@gatech.edu \
    --cc=changwoo@gatech.edu \
    --cc=csong84@gatech.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sanidhya@gatech.edu \
    --cc=taesoo@gatech.edu \
    --cc=tsgatesv@gmail.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 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®