X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Sat, 4 Sep 2010 10:50:40 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: 1.7.7: Cannot unmount certain user bind mounts Message-ID: <20100904085040.GD16534@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3C031C390CBF1E4A8CE1F74DE7ECAF3A158EDA702F@MBX8.EXCHPROD.USA.NET> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <3C031C390CBF1E4A8CE1F74DE7ECAF3A158EDA702F@MBX8.EXCHPROD.USA.NET> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Sep 3 17:19, John Carey wrote: > A user mount whose only non-default option is "bind" > cannot be unmounted if its target is a system mount; > please see the end of this email for a test case. > > It looks to me as if the MOUNT_SYSTEM bit is copied from > the bind target by mount() in winsup/cygwin/mount.cc. Right. I fixed this in CVS. I also fixed the problem that bind mounts in the user's fstab file were preserving the targets MOUNT_SYSTEM flag. And while I was at it, I found that `mount -a' also adds the MOUNT_SYSTEM flag if the added mount is from /etc/fstab. That wasn't intended either. Every mount added via mount(2) is supposed to be a user mount. Thanks for the testcase, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple