Revision fbaf94ee3cd5cfa85fe2d4d04be968820cb00556 authored by Miklos Szeredi on 28 June 2017, 11:41:22 UTC, committed by Miklos Szeredi on 28 June 2017, 11:41:22 UTC
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: Miklos Szeredi <mszeredi@redhat.com>
Fixes: 3a1e819b4e80 ("ovl: store file handle of lower inode on copy up")
1 parent e85f82f
History

README.AddingFirmware

back to top