diff options
author | David Howells <dhowells@redhat.com> | 2019-12-09 15:04:45 +0000 |
---|---|---|
committer | David Howells <dhowells@redhat.com> | 2019-12-11 16:56:54 +0000 |
commit | 158d58335393af3956a9c06f0816ee75ed1f1447 (patch) | |
tree | 383c9c3d800dd07ded0d4c89ff4b8966b48a6d34 /fs/afs/vlclient.c | |
parent | bcbccaf2edcf1b76f73f890e968babef446151a4 (diff) | |
download | linux-158d58335393af3956a9c06f0816ee75ed1f1447.tar.gz linux-158d58335393af3956a9c06f0816ee75ed1f1447.tar.bz2 linux-158d58335393af3956a9c06f0816ee75ed1f1447.zip |
afs: Fix mountpoint parsing
Each AFS mountpoint has strings that define the target to be mounted. This
is required to end in a dot that is supposed to be stripped off. The
string can include suffixes of ".readonly" or ".backup" - which are
supposed to come before the terminal dot. To add to the confusion, the "fs
lsmount" afs utility does not show the terminal dot when displaying the
string.
The kernel mount source string parser, however, assumes that the terminal
dot marks the suffix and that the suffix is always "" and is thus ignored.
In most cases, there is no suffix and this is not a problem - but if there
is a suffix, it is lost and this affects the ability to mount the correct
volume.
The command line mount command, on the other hand, is expected not to
include a terminal dot - so the problem doesn't arise there.
Fix this by making sure that the dot exists and then stripping it when
passing the string to the mount configuration.
Fixes: bec5eb614130 ("AFS: Implement an autocell mount capability [ver #2]")
Reported-by: Jonathan Billings <jsbillings@jsbillings.org>
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Marc Dionne <marc.dionne@auristor.com>
Tested-by: Jonathan Billings <jsbillings@jsbillings.org>
Diffstat (limited to 'fs/afs/vlclient.c')
0 files changed, 0 insertions, 0 deletions