Bug 909866

Description of problem:

The mount command is too aggressive in interpreting "=" chars in device names and makes some operations impossibles, for example fuse.unionfs mounts or mounts with unusual device names.


Version-Release number of selected component (if applicable):

util-linux-2.21.2-3.fc17.x86_64


How reproducible:

Trivially, every time.


Steps to Reproduce:

1. make a few dirs
# mkdir /tmp/{a,b,a_on_b}

2. populate them
# touch a/aaa b/bbb

3. let's try to do a fuse.unionfs mount on fstab
/tmp/a=RW:/tmp/b=RO /tmp/a_on_b fuse.unionfs cow 0 0

4. mount it
# mount /tmp/a_on_b

Actual results:

mount: /tmp/a_on_b: mount failed: Invalid argument


Expected results:

A successful mount.

Additional info:

Trying manually does not solve the issue:
# mount /tmp/a\=RW:/tmp/b\=RO /tmp/a_on_b -t fuse.unionfs -o cow
mount: /tmp/a_on_b: mount failed: Invalid argument

Trying to escape the =
/tmp/a\075RW:/tmp/b\075RO /tmp/a_on_b fuse.unionfs cow 0 0
still does not work.

Please note that I'm using my own rpm derived from
http://podgorny.cz/moin/UnionFsFuse
but the issue is actually on the mount command.
If I recompile the /usr/bin/unionfs to accept "!" instead of "="
and modify my fstab, everything is ok, as mount is not confused anymore.


Another very simple test, non involving unionfs, also fails:

# mkdir /tmp/f=1 /tmp/f1
# mount --bind /tmp/f=1 /tmp/f1
mount: you must specify the filesystem type
# mkdir f-1
# mount --bind /tmp/f-1 /tmp/f1
#

because mount is confused by the "=".

And no luck with fstab too:
both
/tmp/f=1 /tmp/f1 bind bind 0 0
and
/tmp/f\0751 /tmp/f1 bind bind 0 0
fail.