Date: Wed, 29 Sep 2021 06:37:06 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 258208] [zfs] locks up when using rollback or destroy on both 13.0-RELEASE & sysutils/openzfs port Message-ID: <bug-258208-3630-Jkq2sLU9vq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-258208-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-258208-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=3D258208 --- Comment #8 from Andriy Gapon <avg@FreeBSD.org> --- Another potential solution -- and I have / had a prototype for it (it's for= the older FreeBSD ZFS) -- is to have custom lock / unlock vops in ZFS and to en= ter the teardown lock before acquiring the vnode lock. This establishes the lo= ck order friendly to zfs_rezget. There were some tricky details to get that approach working, but I think th= at I got it working in the end. The new order between the teardown and the vnode locks also allowed to simp= lify some code in other vops where currently we have to drop and req-acquire the teardown lock each time we need to get the vnode lock. --=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-258208-3630-Jkq2sLU9vq>