From: Tvrtko Ursulin <tvrtko.ursulin@onelan.co.uk>
To: Ram Pai <linuxram@us.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: Change in behaviour when unmounting recursive bind mounts
Date: Thu, 28 Mar 2013 13:05:56 +0000 [thread overview]
Message-ID: <1694652.5MYOe5IR6S@deuteros> (raw)
In-Reply-To: <20130328030351.GA2033@ram.oc3035372033.ibm.com>
Hi,
On Thursday 28 March 2013 11:03:51 Ram Pai wrote:
> I tried these commands on a 3.8.0-rc1+ kernel and did not find the
> problem. Is this on a recent kernel?
I am on Fedora 17 latest, but I've seen this problem with different kernels.
Pretty sure from 3.5 something to 3.8 something. All Fedora flavoured. I will
try vanilla soon.
What I am not sure is whether this behaviour was there from the start (on
Fedora 17). I *think* it started to happen later on, which would mean a
potential userland change somehow causes it.
Would that be at all possible with some mechanism?
> > Previously unmounting the recursive bind target would not unmount the
> > source, which to me looks like a more sensible outcome.
>
> yes. it should not unless they are peer-mounts, which in your case is
> not.
What are these and how to create them?
Thanks,
Tvrtko
next prev parent reply other threads:[~2013-03-28 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 15:30 Change in behaviour when unmounting recursive bind mounts Tvrtko Ursulin
[not found] ` <20130328030351.GA2033@ram.oc3035372033.ibm.com>
2013-03-28 13:05 ` Tvrtko Ursulin [this message]
2013-03-28 13:23 ` Tvrtko Ursulin
[not found] ` <20130328153549.GP6400@ram.oc3035372033.ibm.com>
2013-03-28 16:29 ` Tvrtko Ursulin
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=1694652.5MYOe5IR6S@deuteros \
--to=tvrtko.ursulin@onelan.co.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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).