Bug 1285 - mount --any_bogus_string doesn't error out (standard mount does)
Summary: mount --any_bogus_string doesn't error out (standard mount does)
Status: REOPENED
Alias: None
Product: Busybox
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: PC Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-14 00:48 UTC by Gunter Ohrner
Modified: 2011-05-12 00:33 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gunter Ohrner 2010-03-14 00:48:54 UTC 
Busybox 1.10.2's

  mount -o rbind / mount --rbind

does not act recursively, ie. submounts are missing from the mirrored mount.

See Debian bug #450895 for further details: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450895
Comment 1 Denys Vlasenko 2011-05-09 01:05:33 UTC 
1.10.x did not support rbind mounts. The support for rbind is to appear in 1.19.x only:

commit 19311bfa7b8e8c6effa9c375de9b0eb4338bee12
Author: Roman Borisov <ext-roman.borisov@nokia.com>
Date:   Thu Mar 24 15:08:43 2011 +0300

    mount: add --rbind option support

    Signed-off-by: Roman Borisov <ext-roman.borisov@nokia.com>
Comment 2 Gunter Ohrner 2011-05-09 19:23:38 UTC 
If it's not implemented, the bug is that mount actually accepts the rbind option.

An option which does not give any error should either

a) work or
b) fail with an error message,

but work partially without giving any diagnostics...

If this won't be fixed in the affected busybox versions, maybe close this bug with RESOLVED WONTFIX, but not RESOLVED INVALID.
Comment 3 Denys Vlasenko 2011-05-12 00:28:39 UTC 
(In reply to comment #2)
> If it's not implemented, the bug is that mount actually accepts the rbind
> option.
> 
> An option which does not give any error should either
> 
> a) work or
> b) fail with an error message,
> 
> but work partially without giving any diagnostics...
> 
> If this won't be fixed in the affected busybox versions, maybe close this bug
> with RESOLVED WONTFIX, but not RESOLVED INVALID.

Ah, I see. "mount --bogus" doesn't complain - that's the bug you report here.
Comment 4 Denys Vlasenko 2011-05-12 00:33:47 UTC 
Basically, with standard mount:

"mount -o any_bogus_string qwe rty" = "mount point rty does not exist",
whereas
"mount --any_bogus_string qwe rty" = "unrecognized option '--any_bogus_string'"

Bbox mount always does the first thing.
Presumably, it will even attempt the mount if given valid DEV and/or DIR args (didn't try).
Looks like a real bug.