ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: jeff.liu <jeff.liu@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Update VFS inode's id info after reflink.
Date: Thu, 22 Apr 2010 15:05:32 +0800	[thread overview]
Message-ID: <4BCFF53C.9000905@oracle.com> (raw)
In-Reply-To: <20100421223652.GI17187@wotan.suse.de>

I have just verified this patch, it works fine for me.

Thanks,
-Jeff

Mark Fasheh wrote:
> On Wed, Apr 21, 2010 at 02:05:55PM +0800, Tao Ma wrote:
>> In reflink we update the id info in the disk but forget to update
>> the corresponding information in the VFS inode. So update them
>> accordingly in case we want to preserve the attributes.
>>
>> Reported-by: Jeff Liu <jeff.liu@oracle.com>
>> Signed-off-by: Tao Ma <tao.ma@oracle.com>
>> ---
>>  fs/ocfs2/refcounttree.c |    3 +++
>>  1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/fs/ocfs2/refcounttree.c b/fs/ocfs2/refcounttree.c
>> index 8ae65c9..a8e8572 100644
>> --- a/fs/ocfs2/refcounttree.c
>> +++ b/fs/ocfs2/refcounttree.c
>> @@ -4083,6 +4083,9 @@ static int ocfs2_complete_reflink(struct inode *s_inode,
>>  	di->i_attr = s_di->i_attr;
>>  
>>  	if (preserve) {
>> +		t_inode->i_uid = s_inode->i_uid;
>> +		t_inode->i_gid = s_inode->i_gid;
>> +		t_inode->i_mode = s_inode->i_mode;
>>  		di->i_uid = s_di->i_uid;
>>  		di->i_gid = s_di->i_gid;
>>  		di->i_mode = s_di->i_mode;
> 
> 
> Looks reasonable to me.
> 
> Acked-by: Mark Fasheh <mfasheh@suse.com>
> 	--Mark
> 
> --
> Mark Fasheh
> 
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel

  reply	other threads:[~2010-04-22  7:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21  6:05 [Ocfs2-devel] [PATCH] ocfs2: Update VFS inode's id info after reflink Tao Ma
2010-04-21 22:36 ` Mark Fasheh
2010-04-22  7:05   ` jeff.liu [this message]
2010-04-23 21:44 ` Joel Becker

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=4BCFF53C.9000905@oracle.com \
    --to=jeff.liu@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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;
as well as URLs for NNTP newsgroup(s).