Your message dated Thu, 31 Oct 2013 14:34:21 -0400
with message-id <[email protected]>
and subject line Read-only bind mounts aren't
has caused the Debian Bug report #441375,
regarding Read-only bind mounts aren't
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
441375: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441375
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mount
Version: 2.12r-19
Severity: normal
After creating a bind mount with "-o ro" I can still write to the target
directory.
Repro (notice how I can create a file in the readonly directory):
"
foo:/tmp# mkdir writable
foo:/tmp# touch writable/fluff
foo:/tmp# mkdir readonly
foo:/tmp# mount -o ro --bind writable/ readonly/
foo:/tmp# ls writable/ readonly/
readonly/:
fluff
writable/:
fluff
foo:/tmp# touch readonly/inconceivable
foo:/tmp# ls writable/ readonly/
readonly/:
fluff inconceivable
writable/:
fluff inconceivable
foo:/tmp# mount | grep writable
/tmp/writable on /tmp/readonly type none (ro,bind)
"
When creating a bind mount with "-o ro" I would like the target directory to be
read
only.
Regards //Johan
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-2-686 (SMP w/2 CPU cores)
Locale: LANG=sv_SE.ISO-8859-15, LC_CTYPE=sv_SE.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages mount depends on:
ii libblkid1 1.40.2-1 block device id library
ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries
ii libuuid1 1.40.2-1 universally unique id library
mount recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Version: 2.17.2-9
Looks like this was applied upstream a long time ago.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJScqKtAAoJEJrBOlT6nu75PUgIAMbkw1HG6bkY5hrYQOLU4Jq4
W+VTkKeeeZU8HTUtCOHNpDFUDSB9ZvObuqgRSGxGaKlFUl1UwOd06L28V4eyUijg
qXY2F66KglNzMY4HBQgnq6XYz/vCrxEuFlyH/7DOL4jsD2tzRIcbQl128Ii9w89W
GoCv6H9+2Lh2KxlnYQMn5GR9TzrOME9bykOct/vGyayv2I6axlh3+BKnQNXXhy9D
RGbEyAB8xN2xecJfLfsy392/579yZ/aVB7HzKE5dyjx/j8thANnPUiseeIxQeJFS
MKsI3FcaeoAsFTN3p/8nsoKlfBtDoV6wyxsX+Gj7d+4Kkk5yV4jYTcdGTpoLfks=
=iwIp
-----END PGP SIGNATURE-----
--- End Message ---
