summaryrefslogtreecommitdiff
path: root/crypto/memneq.c
diff options
context:
space:
mode:
authorAmir Goldstein <amir73il@gmail.com>2017-06-21 15:28:41 +0300
committerMiklos Szeredi <mszeredi@redhat.com>2017-07-04 23:03:17 +0300
commit359f392ca53e9122cafa5fc103545558b0b85d54 (patch)
treed7baa13c1a31c58967cbe46503ac6763a214d9e2 /crypto/memneq.c
parent54fb347e836faadaed2a5617fb4dd4a4597d0490 (diff)
downloadlinux-359f392ca53e9122cafa5fc103545558b0b85d54.tar.xz
ovl: lookup index entry for copy up origin
When inodes index feature is enabled, lookup in indexdir for the index entry of lower real inode or copy up origin inode. The index entry name is the hex representation of the lower inode file handle. If the index dentry in negative, then either no lower aliases have been copied up yet, or aliases have been copied up in older kernels and are not indexed. If the index dentry for a copy up origin inode is positive, but points to an inode different than the upper inode, then either the upper inode has been copied up and not indexed or it was indexed, but since then index dir was cleared. Either way, that index cannot be used to indentify the overlay inode. If a positive dentry that matches the upper inode was found, then it is safe to use the copy up origin st_ino for upper hardlinks, because all indexed upper hardlinks are represented by the same overlay inode as the copy up origin. Set the INDEX type flag on an indexed upper dentry. A non-upper dentry may also have a positive index from copy up of another lower hardlink. This situation will be handled by following patches. Index lookup is going to be used to prevent breaking hardlinks on copy up. Signed-off-by: Amir Goldstein <amir73il@gmail.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'crypto/memneq.c')
0 files changed, 0 insertions, 0 deletions