Skip to content
Snippets Groups Projects
  • Miklos Szeredi's avatar
    fbaf94ee
    ovl: don't set origin on broken lower hardlink · fbaf94ee
    Miklos Szeredi authored
    
    When copying up a file that has multiple hard links we need to break any
    association with the origin file.  This makes copy-up be essentially an
    atomic replace.
    
    The new file has nothing to do with the old one (except having the same
    data and metadata initially), so don't set the overlay.origin attribute.
    
    We can relax this in the future when we are able to index upper object by
    origin.
    
    Signed-off-by: default avatarMiklos Szeredi <mszeredi@redhat.com>
    Fixes: 3a1e819b ("ovl: store file handle of lower inode on copy up")
    fbaf94ee
    History
    ovl: don't set origin on broken lower hardlink
    Miklos Szeredi authored
    
    When copying up a file that has multiple hard links we need to break any
    association with the origin file.  This makes copy-up be essentially an
    atomic replace.
    
    The new file has nothing to do with the old one (except having the same
    data and metadata initially), so don't set the overlay.origin attribute.
    
    We can relax this in the future when we are able to index upper object by
    origin.
    
    Signed-off-by: default avatarMiklos Szeredi <mszeredi@redhat.com>
    Fixes: 3a1e819b ("ovl: store file handle of lower inode on copy up")