Date: Thu, 20 Oct 2005 05:33:31 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Brian Fundakowski Feldman <green@FreeBSD.org> Cc: Pawel Jakub Dawidek <pjd@FreeBSD.org>, FreeBSD current mailing list <current@FreeBSD.org> Subject: Re: mount memory modified after free Message-ID: <Pine.BSF.4.53.0510200532250.52549@e0-0.zab2.int.zabbadoz.net> In-Reply-To: <20051019221804.GA43031@green.homeunix.org> References: <Pine.BSF.4.53.0510151551460.28204@e0-0.zab2.int.zabbadoz.net> <20051016194819.GB3017@garage.freebsd.pl> <20051019221804.GA43031@green.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 19 Oct 2005, Brian Fundakowski Feldman wrote: > On Sun, Oct 16, 2005 at 09:48:19PM +0200, Pawel Jakub Dawidek wrote: > > On Sat, Oct 15, 2005 at 04:00:08PM +0000, Bjoern A. Zeeb wrote: > > +> Hi, > > +> > > +> I had /dev/ad8s4d mounted read only to /shared and > > +> /local/building/ports/shared, then unounted /shared and did a > > +> mount -u -o rw /local/building/ports/shared *kaboom* > > > > This is known problem. Multiple read-only mounts aren't safe. > > Do you mean that multiply-mounting both read-write and read-only isn't > safe? I don't think multiple read-only mounts are unsafe. multi-mounts with one or more r/w are not allowed imho. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.53.0510200532250.52549>