| commit | 09e10322b71716adf567d453889ef0871cf226b9 | |
| author | Miklos Szeredi <mszeredi@suse.cz> | |
| Fri, 12 Dec 2014 23:59:45 +0000 (13 00:59 +0100) | ||
| committer | Miklos Szeredi <mszeredi@suse.cz> | |
| Fri, 12 Dec 2014 23:59:45 +0000 (13 00:59 +0100) | ||
| tree | 5c2287a55fbdf929e6131834c686a888046b5def | treesnapshot (tar.gz zip) |
| parent | 3e01cee3b980f96463cb6f378ab05303a99903d9 | commitdiff |
ovl: lookup ENAMETOOLONG on lower means ENOENT
"Suppose you have in one of the lower layers a filesystem with
->lookup()-enforced upper limit on name length. Pretty much every local fs
has one, but... they are not all equal. 255 characters is the common upper
limit, but e.g. jffs2 stops at 254, minixfs upper limit is somewhere from
14 to 60, depending upon version, etc. You are doing a lookup for
something that is present in upper layer, but happens to be too long for
one of the lower layers. Too bad - ENAMETOOLONG for you..."
Reported-by: Al Viro <viro@ZenIV.linux.org.uk>
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
"Suppose you have in one of the lower layers a filesystem with
->lookup()-enforced upper limit on name length. Pretty much every local fs
has one, but... they are not all equal. 255 characters is the common upper
limit, but e.g. jffs2 stops at 254, minixfs upper limit is somewhere from
14 to 60, depending upon version, etc. You are doing a lookup for
something that is present in upper layer, but happens to be too long for
one of the lower layers. Too bad - ENAMETOOLONG for you..."
Reported-by: Al Viro <viro@ZenIV.linux.org.uk>
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
| fs/overlayfs/super.c | diffblobblamehistory |