Date: Thu, 20 Oct 2005 21:30:11 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Brian Fundakowski Feldman <green@FreeBSD.org> Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, Pawel Jakub Dawidek <pjd@FreeBSD.org>, FreeBSD current mailing list <current@FreeBSD.org> Subject: Re: mount memory modified after free Message-ID: <26671.1129836611@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 20 Oct 2005 11:07:39 EDT." <20051020150739.GB43031@green.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20051020150739.GB43031@green.homeunix.org>, Brian Fundakowski Feldm an writes: >On Thu, Oct 20, 2005 at 08:51:33AM +0200, Poul-Henning Kamp wrote: >> In message <20051020063303.GA19624@garage.freebsd.pl>, Pawel Jakub Dawidek writ >> es: >> >> >Bascially there is only one place to store mount-point's >> >vnode in device structure (IIRC) and if you mount the same provider twice, >> >it will be overwritten and you'll not be able to unmount first file system >> >without panicing. >> >> There is more, you also need to cope with the UFS snapshot data hung >> off the cdev etc. > >There's UFS snapshot data for read-only mounts? Yes, why shouldn't you be able to access snapshots just because you mount r/o ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26671.1129836611>