Date: Tue, 27 Mar 2001 22:24:04 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: iedowse@FreeBSD.ORG Cc: andrew@erlenstar.demon.co.uk, freebsd-bugs@FreeBSD.ORG Subject: Re: kern/4265: Panic in dsinit when multiple FreeBSD slices exist on one disk Message-ID: <Pine.BSF.4.21.0103272205070.12172-100000@besplex.bde.org> In-Reply-To: <200103262346.f2QNkXL76828@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 26 Mar 2001 iedowse@FreeBSD.ORG wrote: > Synopsis: Panic in dsinit when multiple FreeBSD slices exist on one disk > > State-Changed-From-To: open->feedback > State-Changed-By: iedowse > State-Changed-When: Mon Mar 26 15:45:29 PST 2001 > State-Changed-Why: > Is this still a problem in more recent releases? Not really. This was fixed initially mainly by adding some locking to the (pre-cam) scsi driver. The wd driver already had sufficient (I hope) locking. It needed it more because old versions of the driver did even more (and more stateful) i/o than dsopen(). Now the locking has moved to subr_disk.c:diskopen() for disk drivers that use the generic disk interface. The locking there depends on the Giant lock. Most or all non-scsi cdrom drivers get locking stuff wrong, but they don't call dsopen so this is not directly relevant to the PR :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0103272205070.12172-100000>