From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
Description of problem:
I wanted to bind-mount a directory read-only so that I could safely make it
visible through ftp, but, alas, it isn't read-only 00 it looks as though the
read-only flag is ignored even though it appears in the output of "mount".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. mkdir /tmp/xxx /tmp/yyy
2. mount -o ro,bind /tmp/xxx /tmp/yyy
3. touch /tmp/yyy/this-should-not-work
Actual Results: Each command reports everything OK and the file is created.
Expected Results: I was rather hoping to get a "read-only filesystem" error.
"mount | grep /tmp" shows
/tmp/xxx on /tmp/yyy type none (ro,bind)
which rather suggests that /tmp/yyy should be read-only, but "grep /tmp
/dev/sheep/root /tmp/yyy reiserfs rw 0 0
which rather suggests it doesn't. I have an ext3 bind as well which exhibits
the same characteristics.
This is with kernel-2.4.18-24.8.0 and mount-2.11r-10.
This may well be a combination between a bug and an enhancement request if the
kernel doesn't support a read-only bind.
Can't change mount options with --bind
*** This bug has been marked as a duplicate of 77962 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.