From: Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Miklos Szeredi <miklos-sUDqSbJrdHQHWmgEVkV9KA@public.gmane.org>
Cc: Phillip Susi <psusi-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>,
util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux-Fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> 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-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-12-13 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52A878C5.6050505@ubuntu.com>
[not found] ` <20131212120544.GJ16572@x2.net.home>
2013-12-12 19:42 ` read only bind mount ignores ready only Miklos Szeredi
[not found] ` <CAJfpegvWeEb7Dtk8CMxLO4DB-xSLQMxLxccUPReU0GeQ=9d5MA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=miklos-sUDqSbJrdHQHWmgEVkV9KA@public.gmane.org \
--cc=psusi-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
--cc=util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).