public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Phillip Susi <psusi@ubuntu.com>,
	util-linux@vger.kernel.org,
	Linux-Fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: read only bind mount ignores ready only
Date: Fri, 13 Dec 2013 09:18:48 +0100	[thread overview]
Message-ID: <20131213081848.GM16572@x2.net.home> (raw)
In-Reply-To: <CAJfpegvWeEb7Dtk8CMxLO4DB-xSLQMxLxccUPReU0GeQ=9d5MA@mail.gmail.com>

On Thu, Dec 12, 2013 at 08:42:54PM +0100, Miklos Szeredi wrote:
> On Thu, Dec 12, 2013 at 1:05 PM, Karel Zak <kzak@redhat.com> wrote:
> > Miklos would be possible to fix kernel to accept MS_REC for
> > MS_REMOUNT|MS_BIND|MS_RDONLY operation? Please.
> 
> I really hate the current mount(2) API. It's a gigantic hack, and it's

 We all hate it, but we have to use it every day..

> nearing the end of its life anyway due to flags running out.

 well, the current problem with MS_REC is just one small inconsistence
 in the current MS_REMOUNT|MS_BIND semantic. It would be really nice
 to fix it now.

> So instead of adding more hacks, I think it would be better to think
> about adding a couple of syscalls that have clearly defined semantics.

 Yes, but it's (very) long term goal...

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

      parent reply	other threads:[~2013-12-13  8:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 14:37 read only bind mount ignores ready only Phillip Susi
2013-12-11 16:49 ` Karel Zak
2013-12-12 12:05 ` Karel Zak
2013-12-12 14:59   ` Phillip Susi
2013-12-12 16:02     ` Karel Zak
2013-12-12 19:42   ` Miklos Szeredi
2013-12-12 21:53     ` Al Viro
2013-12-13 10:45       ` Karel Zak
2013-12-13  8:18     ` Karel Zak [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131213081848.GM16572@x2.net.home \
    --to=kzak@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=psusi@ubuntu.com \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox