Date: Sun, 22 Dec 2024 18:59:43 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 283448] [fusefs] use after free on NFS-exported file fuse systems Message-ID: <bug-283448-227-hujQTWvIUe@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-283448-227@https.bugs.freebsd.org/bugzilla/> References: <bug-283448-227@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=3D283448 Alan Somers <asomers@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open --- Comment #1 from Alan Somers <asomers@FreeBSD.org> --- My analysis was slightly wrong: the crash actually happens because there ar= en't any fuse file handles for the file in question during fuse_internal_fsync. = I think that the double-free scenario is still possible; it just wasn't the c= ause of this particular crash. I have a WIP fix. <rant> The FUSE protocol was badly designed. It's impossible to accurately implem= ent it on FreeBSD given the way our VFS works (impossible to accurately impleme= nt on Linux too, for that matter). File handles are one of the worst parts. = Life would be a lot easier if we only tried to support well-designed fuse file systems, instead of trying to support all of them. </rant> --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283448-227-hujQTWvIUe>