[Bug 205725] Lock order reversal in gfs_file_create during zfs unmount

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Feb 16 13:56:13 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205725

Will Green <will at sundivenetworks.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |will at sundivenetworks.com

--- Comment #4 from Will Green <will at sundivenetworks.com> ---
I have seen a similar LOR with GFS when using a file-backed ZFS pool on
FreeBSD-11.0-CURRENT-amd64-20160206-r295345. 

It's easy to reproduce:

# dd bs=1m count=256 if=/dev/zero of=/tmp/disk1
256+0 records in
256+0 records out
268435456 bytes transferred in 0.266620 secs (1006810670 bytes/sec)
# zpool create testpool /tmp/disk1
# zpool destroy testpool

Feb 16 13:53:06 fbsd11 ZFS: vdev state changed, pool_guid=5988351068332835963
vdev_guid=14151074118185943762
Feb 16 13:53:14 fbsd11 kernel: lock order reversal:
Feb 16 13:53:14 fbsd11 kernel: 1st 0xfffff800370c05f0 zfs (zfs) @
/usr/src/sys/kern/vfs_mount.c:1222
Feb 16 13:53:14 fbsd11 kernel: 2nd 0xfffff8007238b240 zfs_gfs (zfs_gfs) @
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/gfs.c:494
Feb 16 13:53:14 fbsd11 kernel: stack backtrace:
Feb 16 13:53:14 fbsd11 kernel: #0 0xffffffff80a7fc60 at witness_debugger+0x70
Feb 16 13:53:14 fbsd11 kernel: #1 0xffffffff80a7fb61 at
witness_checkorder+0xe71
Feb 16 13:53:14 fbsd11 kernel: #2 0xffffffff809ff22b at __lockmgr_args+0xd3b
Feb 16 13:53:14 fbsd11 kernel: #3 0xffffffff80ac64fc at vop_stdlock+0x3c
Feb 16 13:53:14 fbsd11 kernel: #4 0xffffffff80fbdb00 at VOP_LOCK1_APV+0x100
Feb 16 13:53:14 fbsd11 kernel: #5 0xffffffff80ae71ba at _vn_lock+0x9a
Feb 16 13:53:14 fbsd11 kernel: #6 0xffffffff820a2b13 at gfs_file_create+0x73
Feb 16 13:53:14 fbsd11 kernel: #7 0xffffffff820a2bbd at gfs_dir_create+0x1d
Feb 16 13:53:14 fbsd11 kernel: #8 0xffffffff8216bf57 at
zfsctl_mknode_snapdir+0x47
Feb 16 13:53:14 fbsd11 kernel: #9 0xffffffff820a3135 at gfs_dir_lookup+0x185
Feb 16 13:53:14 fbsd11 kernel: #10 0xffffffff820a361d at gfs_vop_lookup+0x1d
Feb 16 13:53:14 fbsd11 kernel: #11 0xffffffff8216af75 at
zfsctl_root_lookup+0xf5
Feb 16 13:53:14 fbsd11 kernel: #12 0xffffffff8216be13 at
zfsctl_umount_snapshots+0x83
Feb 16 13:53:14 fbsd11 kernel: #13 0xffffffff82184cfb at zfs_umount+0x7b
Feb 16 13:53:14 fbsd11 kernel: #14 0xffffffff80acfeb0 at dounmount+0x530
Feb 16 13:53:14 fbsd11 kernel: #15 0xffffffff80acf8ed at sys_unmount+0x35d
Feb 16 13:53:14 fbsd11 kernel: #16 0xffffffff80e6f15b at amd64_syscall+0x2db
Feb 16 13:53:14 fbsd11 kernel: #17 0xffffffff80e4ed5b at Xfast_syscall+0xfb

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-amd64 mailing list