From: Al Viro <viro@ftp.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linuxram@us.ibm.com
Subject: Re: [PATCH 13/18] shared mounts handling: move
Date: Wed, 9 Nov 2005 14:33:15 +0000 [thread overview]
Message-ID: <20051109143315.GW7992@ftp.linux.org.uk> (raw)
In-Reply-To: <E1EZnuQ-0001Bg-00@dorka.pomaz.szeredi.hu>
On Wed, Nov 09, 2005 at 12:14:30PM +0100, Miklos Szeredi wrote:
> > From: Ram Pai <linuxram@us.ibm.com>
> > Date: 1131402003 -0500
> >
> > Handling of mount --move in presense of shared mounts (see
> > Documentation/sharedsubtree.txt in the end of patch series
> > for detailed description).
>
> This patch seems to be totally wrong. It copies the mounts instead of
> moving them in the propagated cases.
>
> Am I missing something?
Yes, you are. We move a single subtree (which has no peers at all)
to mountpoint that gives propagation. The subtree itself gets moved
to specified mountpoint; for the rest of points in propagation tree
of that mountpoint we have no choice but to create copies.
prev parent reply other threads:[~2005-11-09 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 2:01 [PATCH 13/18] shared mounts handling: move Al Viro
2005-11-09 11:14 ` Miklos Szeredi
2005-11-09 14:33 ` Al Viro [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=20051109143315.GW7992@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=miklos@szeredi.hu \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.