Date: Mon, 30 Apr 2018 06:49:41 +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-CGCrCLhjTS@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 --- Comment #6 from Damjan Jovanovic <damjan.jov@gmail.com> --- Repeating that test with UFS (newfs -U -j) also freezes the system, so sadly msdosfs is not the only filesystem affected. Using the ext2fs driver on a read-only EXT3 filesystem however works, print= ing some errors in dmesg: g_vfs_done():ggate0[WRITE(offset=3D1024, length=3D1024)]error =3D 1 g_vfs_done():ggate0[WRITE(offset=3D1024, length=3D1024)]error =3D 1 g_vfs_done():ggate0[WRITE(offset=3D2048, length=3D1024)]error =3D 1 g_vfs_done():ggate0[WRITE(offset=3D268288, length=3D1024)]error =3D 1 g_vfs_done():ggate0[WRITE(offset=3D268288, length=3D1024)]error =3D 1 but it mounts successfully, denies writes with EPERM, and doesn't crash. Unmounting however fails, with this ominous error: fsync: giving up on dirty (error =3D 1) 0xfffff801df6a45a0: tag devfs, type= VCHR usecount 1, writecount 0, refcount 7 rdev 0xfffff800d1092800 flags (VI_ACTIVE) v_object 0xfffff80146eb3900 ref 0 pages 2 cleanbuf 1 dirtybuf 4 lock type devfs: EXCL by thread 0xfffff800d1017000 (pid 1494, umount, t= id 100515) dev ggate0 but still no crash. --=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-CGCrCLhjTS>