From owner-freebsd-geom@FreeBSD.ORG Sun Feb 1 13:32:50 2004 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CC8216A4CE; Sun, 1 Feb 2004 13:32:50 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4D0243D1F; Sun, 1 Feb 2004 13:32:48 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i11LWju4000719; Sun, 1 Feb 2004 22:32:46 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: Lukas Ertl From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sun, 01 Feb 2004 22:29:54 +0100." <20040201222823.M616@korben.in.tern> Date: Sun, 01 Feb 2004 22:32:45 +0100 Message-ID: <718.1075671165@critter.freebsd.dk> cc: sos@freebsd.org cc: freebsd-geom@freebsd.org Subject: Re: Panic in g_disk_done() with atacontrol detach X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2004 21:32:50 -0000 In message <20040201222823.M616@korben.in.tern>, Lukas Ertl writes: >On Sun, 1 Feb 2004, Poul-Henning Kamp wrote: > >> In message <20040201190653.M613@korben.in.tern>, Lukas Ertl writes: >> >The problem obviously is that ad_detach() calls disk_destroy() which nulls >> >out the softc, and in g_disk_done() this softc is referenced again. >> > >> >The question is: is this an unsupported operation in the sense of "don't >> >do that"? If yes, then "atacontrol detach" should probably refuse to do >> >the actual detach when there are I/O requests running, this would prevent >> >a lot of foot shooting. >> >> No, this should work. > >Ok, but just commenting out the "gp->softc = NULL" statements apparently >aren't the way to go, cause then I end up in a panic somewhere in the >softupdate code... > >Any hints how to properly do this? I need to look a this in detail before I can answer, but the trick may be to move the removal of the devstat stuff earlier (ie: before the null'ing of the softc). -- 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.