linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Daeho Jeong <daeho43@gmail.com>
To: Yeongjin Gil <youngjin.gil@samsung.com>
Cc: daehojeong@google.com, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
	Sungjong Seo <sj1557.seo@samsung.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: Create COW inode from parent dentry for atomic write
Date: Tue, 13 Aug 2024 10:32:34 -0700	[thread overview]
Message-ID: <CACOAw_y7g6CGCDB4NG7Y-+cg2niYxg4NVpcm5eg717j45GowtQ@mail.gmail.com> (raw)
In-Reply-To: <20240813073244.9052-1-youngjin.gil@samsung.com>

On Tue, Aug 13, 2024 at 12:34 AM Yeongjin Gil <youngjin.gil@samsung.com> wrote:
>
> The i_pino in f2fs_inode_info has the previous parent's i_ino when inode
> was renamed, which may cause f2fs_ioc_start_atomic_write to fail.
> If file_wrong_pino is true and i_nlink is 1, then to find a valid pino,
> we should refer to the dentry from inode.
>
> To resolve this issue, let's get parent inode using parent dentry
> directly.
>
> Fixes: 3db1de0e582c ("f2fs: change the current atomic write way")
> Reviewed-by: Sungjong Seo <sj1557.seo@samsung.com>
> Reviewed-by: Sunmin Jeong <s_min.jeong@samsung.com>
> Signed-off-by: Yeongjin Gil <youngjin.gil@samsung.com>
> ---
>  fs/f2fs/file.c | 12 +++---------
>  1 file changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index fba8b5f216f9..1eae123f0315 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -2127,7 +2127,6 @@ static int f2fs_ioc_start_atomic_write(struct file *filp, bool truncate)
>         struct mnt_idmap *idmap = file_mnt_idmap(filp);
>         struct f2fs_inode_info *fi = F2FS_I(inode);
>         struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
> -       struct inode *pinode;
>         loff_t isize;
>         int ret;
>
> @@ -2178,15 +2177,10 @@ static int f2fs_ioc_start_atomic_write(struct file *filp, bool truncate)
>         /* Check if the inode already has a COW inode */
>         if (fi->cow_inode == NULL) {
>                 /* Create a COW inode for atomic write */
> -               pinode = f2fs_iget(inode->i_sb, fi->i_pino);
> -               if (IS_ERR(pinode)) {
> -                       f2fs_up_write(&fi->i_gc_rwsem[WRITE]);
> -                       ret = PTR_ERR(pinode);
> -                       goto out;
> -               }
> +               struct dentry *dentry = file_dentry(filp);
> +               struct inode *dir = d_inode(dentry->d_parent);
>
> -               ret = f2fs_get_tmpfile(idmap, pinode, &fi->cow_inode);
> -               iput(pinode);
> +               ret = f2fs_get_tmpfile(idmap, dir, &fi->cow_inode);
>                 if (ret) {
>                         f2fs_up_write(&fi->i_gc_rwsem[WRITE]);
>                         goto out;
> --
> 2.40.1
>

Reviewed-by: Daeho Jeong <daehojeong@google.com>

Thanks,

>
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2024-08-13 17:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240813073246epcas1p4085b32d2b008b77119b811dc328b964e@epcas1p4.samsung.com>
2024-08-13  7:32 ` [f2fs-dev] [PATCH] f2fs: Create COW inode from parent dentry for atomic write Yeongjin Gil
2024-08-13 17:32   ` Daeho Jeong [this message]
2024-08-14  3:46   ` Chao Yu
2024-08-30 20:51   ` patchwork-bot+f2fs--- via Linux-f2fs-devel

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=CACOAw_y7g6CGCDB4NG7Y-+cg2niYxg4NVpcm5eg717j45GowtQ@mail.gmail.com \
    --to=daeho43@gmail.com \
    --cc=daehojeong@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sj1557.seo@samsung.com \
    --cc=youngjin.gil@samsung.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).