Re: [RFC][PATCH 20/20] honor r/w changes at do_remount() time

On Fri, Jun 16, 2006 at 04:12:28PM -0700, Dave Hansen wrote:
> 
> Originally from: Herbert Poetzl <[email protected]>
> 
> This is the core of the read-only bind mount patch set.
> 
> Note that this does _not_ add a "ro" option directly to
> the bind mount operation.  If you require such a mount,
> you must first do the bind, then follow it up with a
> 'mount -o remount,ro' operation.

Hrm...  So you want r/o status of vfsmount completely independent from
that of superblock?  I.e. allow writable vfsmount over r/o filesystem?
I realize that we have double checks, but...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC][PATCH 20/20] honor r/w changes at do_remount() time
    • From: Dave Hansen <[email protected]>

• References:
  • [RFC][PATCH 00/20] Mount writer count and read-only bind mounts (v2)
    • From: Dave Hansen <[email protected]>
  • [RFC][PATCH 20/20] honor r/w changes at do_remount() time
    • From: Dave Hansen <[email protected]>

• Prev by Date: Re: Support for SEEK_HOLE and SEEK_DATA for sparse files on lseek(2)
• Next by Date: Re: [RFC] [patch 0/6] [Network namespace] introduction
• Previous by thread: [RFC][PATCH 20/20] honor r/w changes at do_remount() time
• Next by thread: Re: [RFC][PATCH 20/20] honor r/w changes at do_remount() time
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]