linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	linuxram@us.ibm.com, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] shared mounts: save mount flag space
Date: Sun, 27 Nov 2005 06:32:16 +0000	[thread overview]
Message-ID: <20051127063216.GC27946@ftp.linux.org.uk> (raw)
In-Reply-To: <20051126215509.073cb957.akpm@osdl.org>

On Sat, Nov 26, 2005 at 09:55:09PM -0800, Andrew Morton wrote:
> > -	else if (flags & (MS_SHARED | MS_PRIVATE | MS_SLAVE | MS_UNBINDABLE))
> > -		retval = do_change_type(&nd, flags);
> > +	else if (flags & MS_PROPAGATION)
> > +		retval = do_change_type(&nd, flags & MS_REC, data_page);
> >  	else if (flags & MS_MOVE)
> >  		retval = do_move_mount(&nd, dev_name);
> >  	else
> 
> But I don't know how much trauma this would cause.  Hasn't util-linux
> already been patched with the new mount flags?
> 
> If it has, and if it uses the same names for these options, the patched
> mount(8) just won't work.
> 
> The proposed new mount options should be documented somewhere.
> 
> Anyway, I'll let Ram&Al decide on this proposal.

It's
	a) palliative
	b) ugly

Let's face it, mount(2) ABI is getting past its shelf life already.
We'll need saner replacement (not mixing action with the flags and
being really typed) anyway, so let's not introduce more kludges into
mount(2) already messy situation - it's not worth the effort.

  reply	other threads:[~2005-11-27  6:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-24 16:09 [PATCH 1/2] shared mounts: cleanup Miklos Szeredi
2005-11-24 16:18 ` [PATCH 2/2] shared mounts: save mount flag space Miklos Szeredi
2005-11-24 16:33   ` Miklos Szeredi
2005-11-27  5:55     ` Andrew Morton
2005-11-27  6:32       ` Al Viro [this message]
2005-11-27  9:34         ` Miklos Szeredi
2005-11-28 12:14       ` Ram Pai
2005-11-29 12:30       ` Rob Landley

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=20051127063216.GC27946@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxram@us.ibm.com \
    --cc=miklos@szeredi.hu \
    /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).