lkml.org 
[lkml]   [2017]   [May]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 4/6] ubifs: Maintain a parent pointer
Hi Richard,

On Mon, May 22, 2017 at 10:45:08AM +0200, Richard Weinberger wrote:
> Hyunchul,
>
> Am 22.05.2017 um 06:30 schrieb Hyunchul Lee:
> >> + if (move)
> >> + old_inode_ui->parent_inum = new_dir->i_ino;
> >> +
> >> err = ubifs_jnl_rename(c, old_dir, old_inode, &old_nm, new_dir,
> >> new_inode, &new_nm, whiteout, sync);
> >
> > I think that old_inode_ui->parent_inum could point old_dir, even though old_inode
> > is a child of new_dir. this could happen that there is power-cut before
> > old_inode is synced. so I guess that old_inode is needed to be written with
> > rename's node group in ubifs_jnl_rename. is it right?
>
> I assumed that the journal does this already because we change old_inode->i_ctime
> in this function too.
> But checking the code showed the opposite.
> So, if we face a power-cut the rename can succeed but we lose the ctime change.
>
> This needs to be addressed before we can add the parent pointer.

Is writing old_inode->i_ctime required? I guess that it is needed only when
IS_SYNC(old_inode) is true, otherwise we don't need to guarantee that ctime
is synced.

>
> Thanks,
> //richard
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

--

Thanks,
Hyunchul

\
 
 \ /
  Last update: 2017-05-23 01:51    [W:0.046 / U:0.100 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site