Re: [PATCH 0/6 v7] overlay filesystem - request for inclusion

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 22 Mar 2011, Al Viro wrote:
> Proceeding with rename is not interesting; proceeding with copyup is.
> 
> Who said that by the time we get to copy_up_locked you will still have
> dentry (and upper) match lowerpath?  Or that ->d_parent on overlay and
> on upper will change in sync, for that matter - there are two d_move()
> calls involved...

If rename is involved, than rename itself already did the copy up.
And that's checked before proceeding with the actual copy up.  If
there was no rename, then that guarantees that things are in sync, at
least for the duration of the copy up.

Is that not enough?

Thanks,
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux