Date: Mon, 30 Apr 2018 05:18:12 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 210316] panic after trying to r/w mount msdosfs on write protected media Message-ID: <bug-210316-3630-feY4ceKkmT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-210316-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-210316-3630@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=3D210316 Damjan Jovanovic <damjan.jov@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |damjan.jov@gmail.com --- Comment #5 from Damjan Jovanovic <damjan.jov@gmail.com> --- Still a problem on CURRENT. Very easy to reproduce: dd if=3D/dev/zero of=3D/path/to/image bs=3D1M count=3D100 newfs_msdos /path/to/image ggatel create -o ro /path/to/image mount /dev/ggate0 /mnt A few seconds later: crash. I wonder what the best way to fix this is. Should the referenced geom explicitly be cleared from the buffer after the failed write? Should the msdosfs driver call fsync() before g_vfs_destroy()-ing the geom on mount failure, so the dirty buffer is deleted before the geom device it reference= s is deleted? Should geom devices be reference counted by their buffers and be forced to live until all buffers that reference them are deleted? --=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-210316-3630-feY4ceKkmT>