diff options
| author |   Miklos Szeredi <mszeredi@redhat.com> | 2018-11-01 21:31:39 +0100 |
|---|---|---|
| committer | Miklos Szeredi <mszeredi@redhat.com> | 2018-11-01 21:31:39 +0100 |
| commit | d47748e5ae5af6572e520cc9767bbe70c22ea498 (patch) | |
| tree | ae33bdfffaaa6c1e9297d33f39dff2ddee4ddb24 /crypto | |
| parent | ovl: check whiteout in ovl_create_over_whiteout() (diff) | |
| download | linux-dev-d47748e5ae5af6572e520cc9767bbe70c22ea498.tar.xz linux-dev-d47748e5ae5af6572e520cc9767bbe70c22ea498.zip | |
ovl: automatically enable redirect_dir on metacopy=on
Current behavior is to automatically disable metacopy if redirect_dir is
not enabled and proceed with the mount.
If "metacopy=on" mount option was given, then this behavior can confuse the
user: no mount failure, yet metacopy is disabled.
This patch makes metacopy=on imply redirect_dir=on.
The converse is also true: turning off full redirect with redirect_dir=
{off|follow|nofollow} will disable metacopy.
If both metacopy=on and redirect_dir={off|follow|nofollow} is specified,
then mount will fail, since there's no way to correctly resolve the
conflict.
Reported-by: Daniel Walsh <dwalsh@redhat.com>
Fixes: d5791044d2e5 ("ovl: Provide a mount option metacopy=on/off...")
Cc: <stable@vger.kernel.org> # v4.19
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions