Date: Mon, 03 Jan 2022 03:46:24 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 251342] fs/unionfs: VOP_UNSET_TEXT without VOP_SET_TEXT leads to panic Message-ID: <bug-251342-3630-G00XcpVlyK@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-251342-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-251342-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=3D251342 --- Comment #1 from commit-hook@FreeBSD.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3D9e891d43f586e91541bd61fb12550de29= 6d76fd9 commit 9e891d43f586e91541bd61fb12550de296d76fd9 Author: Jason A. Harmening <jah@FreeBSD.org> AuthorDate: 2021-12-21 23:51:51 +0000 Commit: Jason A. Harmening <jah@FreeBSD.org> CommitDate: 2022-01-03 03:52:58 +0000 unionfs: implement VOP_SET_TEXT/VOP_UNSET_TEXT The implementation simply passes the text ref to the appropriate underlying vnode. Without this, the default [un]set_text implementation will only manage the text ref on the unionfs vnode, causing it to be out of sync with the underlying filesystems and potentially allowing corruption of executable file contents. On INVARIANTS kernels, it also readily produces a panic on process termination because the VM object representing the executable mapping is backed by the underlying vnode, not the unionfs vnode. PR: 251342 Reviewed by: kib Differential Revision: https://reviews.freebsd.org/D33611 sys/fs/unionfs/union_vnops.c | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) --=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-251342-3630-G00XcpVlyK>