Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Mar 2021 11:14:02 -0700
From:      John-Mark Gurney <jmg@funkthat.com>
To:        Emanuel Haupt <ehaupt@FreeBSD.org>
Cc:        hackers@FreeBSD.org
Subject:   Re: RFC: possible issue with kqueue
Message-ID:  <20210330181402.GM14975@funkthat.com>
In-Reply-To: <20210327131011.e16291cac86475e75a33812c@FreeBSD.org>
References:  <20210327131011.e16291cac86475e75a33812c@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Emanuel Haupt wrote this message on Sat, Mar 27, 2021 at 13:10 +0100:
> Can someone familiar with kqueue please comment on:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254024

Done:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254024#c11

Looks like the user wasn't force unmounting the FS.  There really
isn't any problem w/ kqueue, as a normal unmount is expected to be
refused while files are open.

I guess there COULD be a new flag added to file descriptors that
flag them as being able to be closed upon unmount.  Then when an
unmount happens and only these flagged files remain, they are closed
allowing the fs to unmount.  But this is a new feature and independent
of kqueue.

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210330181402.GM14975>