| Summary: | mount --any_bogus_string doesn't error out (standard mount does) | ||
|---|---|---|---|
| Product: | Busybox | Reporter: | Gunter Ohrner <G.Ohrner> |
| Component: | Other | Assignee: | unassigned |
| Status: | REOPENED --- | ||
| Severity: | normal | CC: | busybox-cvs |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
Gunter Ohrner
2010-03-14 00:48:54 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> 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. (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. 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. |