summaryrefslogtreecommitdiffstats
path: root/cddl/contrib/opensolaris/tools/ctf/cvt/ctfmerge.c
diff options
context:
space:
mode:
authordelphij <delphij@FreeBSD.org>2013-07-30 20:37:32 +0000
committerdelphij <delphij@FreeBSD.org>2013-07-30 20:37:32 +0000
commit744a60053606bf8c3f5c880db82f3e2e7d9484b8 (patch)
treeb0120655a770aebcec34648ef43d149a2859ccff /cddl/contrib/opensolaris/tools/ctf/cvt/ctfmerge.c
parentd74088447ca18d7fe0d6c871d7089bb1949a31bc (diff)
downloadFreeBSD-src-744a60053606bf8c3f5c880db82f3e2e7d9484b8.zip
FreeBSD-src-744a60053606bf8c3f5c880db82f3e2e7d9484b8.tar.gz
MFV r253780:
To quote Illumos #3875: The problem here is that if we ever end up in the error path, we drop the locks protecting access to the zfsvfs_t prior to forcibly unmounting the filesystem. Because z_os is NULL, any thread that had already picked up the zfsvfs_t and was sitting in ZFS_ENTER() when we dropped our locks in zfs_resume_fs() will now acquire the lock, attempt to use z_os, and panic. Illumos ZFS issues: 3875 panic in zfs_root() after failed rollback MFC after: 2 weeks
Diffstat (limited to 'cddl/contrib/opensolaris/tools/ctf/cvt/ctfmerge.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud