Hi, It is well known that --bind -o ro fails silently resulting in a mount that is rw. $ touch a $ touch b $ mount --bind -o ro a b $ mount <...snip...> /home/tez/a on /home/tez/b type none (ro,bind) # <---- Appears as ro, but is rw $ echo abc > b $ cat a abc This is dangerous enough. However, it is totally insane to incorrectly update mtab to indicate that a mount is ro when it is in fact rw so that mount then reports bogus options. This situation has now persisted for more than 18 months and is undoubtedly resulting in security issues for some users. Is a fix planned? Thanks, Terry -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
