From owner-freebsd-geom@freebsd.org Mon Nov 6 08:06:15 2017 Return-Path: Delivered-To: freebsd-geom@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2A4EE567B1 for ; Mon, 6 Nov 2017 08:06:14 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 96C1C64D60 for ; Mon, 6 Nov 2017 08:06:14 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id A28C8273C0; Mon, 6 Nov 2017 08:06:06 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id vA685oDO031858; Mon, 6 Nov 2017 08:05:50 GMT (envelope-from phk@phk.freebsd.dk) To: Colin Percival cc: freebsd-geom@freebsd.org Subject: Re: No automatic root mount holding for new geom providers? In-reply-to: <0100015f900017eb-91becde5-26c8-49f0-b593-751670ca42e0-000000@email.amazonses.com> From: "Poul-Henning Kamp" References: <0100015f900017eb-91becde5-26c8-49f0-b593-751670ca42e0-000000@email.amazonses.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <31856.1509955550.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Mon, 06 Nov 2017 08:05:50 +0000 Message-ID: <31857.1509955550@critter.freebsd.dk> X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Nov 2017 08:06:15 -0000 -------- In message <0100015f900017eb-91becde5-26c8-49f0-b593-751670ca42e0-000000@e= mail. amazonses.com>, Colin Percival writes: >In practice, it seems that we avoid this by virtue of tasting new geoms b= eing >much faster than everything else the kernel does between when the disks a= re >attached and when vfs_mountroot runs, but I wouldn't want to rely on that= . > >Am I missing something? As I recall, the actual open will stall on the non-empty event-queue. -- = 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= .