The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, chao@kernel.org
Subject: Re: [PATCH] f2fs: fix to recover inode's uid/gid during POR
Date: Thu, 20 Sep 2018 14:41:30 -0700	[thread overview]
Message-ID: <20180920214130.GC35918@jaegeuk-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <20180920094130.124622-1-yuchao0@huawei.com>

On 09/20, Chao Yu wrote:
> Step to reproduce this bug:
> 1. logon as root
> 2. mount -t f2fs /dev/sdd /mnt;
> 3. touch /mnt/file;
> 4. chown system /mnt/file; chgrp system /mnt/file;
> 5. xfs_io -f /mnt/file -c "fsync";
> 6. godown /mnt;
> 7. umount /mnt;
> 8. mount -t f2fs /dev/sdd /mnt;
> 
> After step 8) we will expect file's uid/gid are all system, but during
> recovery, these two fields were not been recovered, fix it.

Hmm, I tried this before, but wasn't enough to fix everything. :(

> 
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
>  fs/f2fs/recovery.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
> index ba678efe7cad..da9f59b9044e 100644
> --- a/fs/f2fs/recovery.c
> +++ b/fs/f2fs/recovery.c
> @@ -209,6 +209,8 @@ static void recover_inode(struct inode *inode, struct page *page)
>  	char *name;
>  
>  	inode->i_mode = le16_to_cpu(raw->i_mode);
> +	i_uid_write(inode, le32_to_cpu(raw->i_uid));
> +	i_gid_write(inode, le32_to_cpu(raw->i_gid));
>  	f2fs_i_size_write(inode, le64_to_cpu(raw->i_size));
>  	inode->i_atime.tv_sec = le64_to_cpu(raw->i_atime);
>  	inode->i_ctime.tv_sec = le64_to_cpu(raw->i_ctime);
> -- 
> 2.18.0.rc1

  reply	other threads:[~2018-09-20 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20  9:41 [PATCH] f2fs: fix to recover inode's uid/gid during POR Chao Yu
2018-09-20 21:41 ` Jaegeuk Kim [this message]
2018-09-21  6:06 ` Christoph Hellwig
2018-09-21  6:20   ` Chao Yu
2018-09-21  6:40     ` Christoph Hellwig

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=20180920214130.GC35918@jaegeuk-macbookpro.roam.corp.google.com \
    --to=jaegeuk@kernel.org \
    --cc=chao@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuchao0@huawei.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