Date: Sat, 3 Apr 2021 06:22:36 +0300 From: Rozhuk Ivan <rozhuk.im@gmail.com> To: Ian Lepore <ian@freebsd.org> Cc: John-Mark Gurney <jmg@funkthat.com>, Emanuel Haupt <ehaupt@FreeBSD.org>, hackers@FreeBSD.org Subject: Re: RFC: possible issue with kqueue Message-ID: <20210403062236.526fa1c4@rimwks.local> In-Reply-To: <cef6b9fd5667c7fb227ab646d6f6a0edf11a145b.camel@freebsd.org> References: <20210327131011.e16291cac86475e75a33812c@FreeBSD.org> <20210330181402.GM14975@funkthat.com> <cef6b9fd5667c7fb227ab646d6f6a0edf11a145b.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I wonder if a reasonable fix might be to have some sort of pre-unmount > event that can be delivered via kqueue, so that a userland entity > monitoring on that volume has a chance to close related descriptors so > that the unmount can proceed? > https://reviews.freebsd.org/D19690 I do not finish this. Plan was: implement this and catch unmount notify in my FAM, that in glib20.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210403062236.526fa1c4>