linux-kernel - Re: Change in behaviour when unmounting recursive bind mounts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1694652.5MYOe5IR6S@deuteros>
Date:	Thu, 28 Mar 2013 13:05:56 +0000
From:	Tvrtko Ursulin <tvrtko.ursulin@...lan.co.uk>
To:	Ram Pai <linuxram@...ibm.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org, Al Viro <viro@...iv.linux.org.uk>
Subject: Re: Change in behaviour when unmounting recursive bind mounts

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/