summaryrefslogtreecommitdiff
path: root/fs/overlayfs/Kconfig
diff options
context:
space:
mode:
authorVivek Goyal <vgoyal@redhat.com>2018-02-02 18:23:24 +0300
committerMiklos Szeredi <mszeredi@redhat.com>2018-02-26 18:55:51 +0300
commitd1fe96c0e4de78ba0cd336ea3df3b850d06b9b9a (patch)
treee9bb7accaf4f88d3a0a8e1f940f9377d8ace657a /fs/overlayfs/Kconfig
parentb5095f24e791c2d05da7cbb3d99e2b420b36a273 (diff)
downloadlinux-d1fe96c0e4de78ba0cd336ea3df3b850d06b9b9a.tar.xz
ovl: redirect_dir=nofollow should not follow redirect for opaque lower
redirect_dir=nofollow should not follow a redirect. But in a specific configuration it can still follow it. For example try this. $ mkdir -p lower0 lower1/foo upper work merged $ touch lower1/foo/lower-file.txt $ setfattr -n "trusted.overlay.opaque" -v "y" lower1/foo $ mount -t overlay -o lowerdir=lower1:lower0,workdir=work,upperdir=upper,redirect_dir=on none merged $ cd merged $ mv foo foo-renamed $ umount merged # mount again. This time with redirect_dir=nofollow $ mount -t overlay -o lowerdir=lower1:lower0,workdir=work,upperdir=upper,redirect_dir=nofollow none merged $ ls merged/foo-renamed/ # This lists lower-file.txt, while it should not have. Basically, we are doing redirect check after we check for d.stop. And if this is not last lower, and we find an opaque lower, d.stop will be set. ovl_lookup_single() if (!d->last && ovl_is_opaquedir(this)) { d->stop = d->opaque = true; goto out; } To fix this, first check redirect is allowed. And after that check if d.stop has been set or not. Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Fixes: 438c84c2f0c7 ("ovl: don't follow redirects if redirect_dir=off") Cc: <stable@vger.kernel.org> #v4.15 Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'fs/overlayfs/Kconfig')
0 files changed, 0 insertions, 0 deletions