Date: Thu, 05 May 2022 14:17:29 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 263765] panic: ffs_sync: modification on read-only filesystem Message-ID: <bug-263765-3630-oDlPC4dnfW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-263765-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-263765-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=3D263765 --- Comment #4 from Mark Johnston <markj@FreeBSD.org> --- (In reply to Konstantin Belousov from comment #3) Hmm, above the definition of fs_fmod we even have "/* these fields are clea= red at mount time */", but this is not respected. You're right, there is no synchronization for the fs_fmod field changes. So this is probably not a new bug, but I'm surprised that I never saw it befor= e. > More important, I believe, UFS mount lock should be taken around bcopy() in ffs_use_bwrite(), although there is probably not too many volatile fields which can be corrupted, if any. Such corruptions would presumably be detected by the superblock check hash. (It would be nice if makefs supported enabling check hashes.) --=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-263765-3630-oDlPC4dnfW>