Date: Wed, 08 May 2019 23:59:29 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 214338] [PATCH] devel/glib20: new kqueue() backend for file monitoring Message-ID: <bug-214338-6497-MmvIaTYk94@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-214338-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-214338-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214338 rozhuk.im@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #202935|0 |1 is obsolete| | Attachment #204279| |maintainer-approval? Flags| | --- Comment #74 from rozhuk.im@gmail.com --- Created attachment 204279 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D204279&action= =3Dedit patch update Crash fixes and improvements - Add reaction to mount points changed. - kq_fnme_init_cb() now check is existing fnmo is alive and try to reinit if needed. - Add few additional checks for -1 =3D=3D fnmo->fd (is_removed). - use mem addr as timer id (for EVFILT_TIMER) - split kq_fnmo_init() into kq_fnmo_init() + kq_fnmo_reopen_fd() - fix MSTOSBT macro and comment. - fix: readdir_next() may returns empty entryes without filename - fix: kq_fnmo_readdir() may return already deleted files, that returns from readdir_next() - fix: wrong event "add file" after event "remove file" (die to kq_fnmo_readdir()) - fix: fd leak and may crash on dir remove: use kq_fnmo_reopen_fd() instead= of kq_fnmo_init() - fix: duplicate event about monitoring dir deleted - cosmetic changes... --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214338-6497-MmvIaTYk94>