Date: Fri, 23 Mar 2018 09:30:03 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Andriy Gapon <avg@FreeBSD.org> Cc: Warner Losh <imp@bsdimp.com>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>, freebsd-geom@freebsd.org Subject: Re: geom->access problem and workaround Message-ID: <888.1521797403@critter.freebsd.dk> In-Reply-To: <5e416eb6-0e79-1419-f09a-eb747215dc28@FreeBSD.org> References: <809d9254-ee56-59d8-69a4-08838e985cea@FreeBSD.org> <CANCZdfpPGXbKnMfuXWJFVk3xpk-hj8%2BtnsscbySeQTOrB2M-9w@mail.gmail.com> <56619.1520878022@critter.freebsd.dk> <5e416eb6-0e79-1419-f09a-eb747215dc28@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--------
In message <5e416eb6-0e79-1419-f09a-eb747215dc28@FreeBSD.org>, Andriy Gapo=
n writes:
>On 12/03/2018 20:07, Poul-Henning Kamp wrote:
>> If we want to have an architectural sound way to do slow operations
>> before any "user-I/O" is initiated, the right way to do so is to
>> define new BIO_OPEN and BIO_CLOSE operation, and insist via asserts
>> than all BIO_{READ|WRITE|DELETE} are wrapped in these.
>What do you think?
I don't see that changing anything...
GEOM rests on a set of assumptions, if you violate them, you get panics.
-- =
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?888.1521797403>