Date: Sun, 02 Jan 2022 21:18:31 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260884] [zfs] Panic in zfs_onexit_destroy [fix available] Message-ID: <bug-260884-227-KTH5KPr9Uh@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260884-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260884 --- Comment #3 from Michael Gmelin <grembo@FreeBSD.org> --- (In reply to Ed Maste from comment #2) The fix was imported into stable/13.0 back in March as part of a larger commit: zfs: merge OpenZFS master-9305ff2ed https://cgit.freebsd.org/src/commit/?h=stable/13&id=9db44a8e This pulls in a lot of changes, but lists them separately, the one in question is: #11720 FreeBSD: Clean up zfsdev_close to match Linux (which refers to https://github.com/openzfs/zfs/pull/11720), which is the patch I tested above (https://patch-diff.githubusercontent.com/raw/openzfs/zfs/pull/11720.diff == https://github.com/openzfs/zfs/commit/f845b2dd.diff). To only get these changes from our source tree, look at: A. https://cgit.freebsd.org/src/commit/sys/contrib/openzfs/module/os/freebsd/zfs/kmod_core.c?id=9db44a8e B. https://cgit.freebsd.org/src/commit/sys/contrib/openzfs/include/sys/zfs_ioctl.h?id=9db44a8e Pulling everything from 9db44a8e would basically be an OpenZFS update, but from what I can tell, just pulling in A. and B. from above is enough to correct the problem at hand and should work ok in isolation (second pair of eyes won't hurt). -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260884-227-KTH5KPr9Uh>