CURRENT and smbfs -> lockmgr: thread 0xXXXX unlocking unheld lock

Whenever i mount a samba share, i get this in my logs:

lockmgr: thread 0xc4a14d80 unlocking unheld lock
KDB: stack backtrace:
kdb_backtrace(c06a0a0b,c4a14d80,c6c026f0,e4f4cb5c,c04eec25) at kdb_backtrace+0x2
f
lockmgr(c6c04e08,6,c6c04e2c,c4a14d80,e4f4cb98) at lockmgr+0x604
smb_co_unlock(c6c04e00,0,c4a14d80,c4a14d80,e4f4cbb8) at smb_co_unlock+0x2c
smb_sm_init(e4f4cbb8,c04f1f78,c6741a6c,c6c0283f,c6741a40) at smb_sm_init+0x4a
nsmb_dev_load(c6741a40,0,0,0,102) at nsmb_dev_load+0x1d
module_register_init(c6c042c4,c06a0666,e4f4cbfc,e4f4cc00,0) at module_register_i
nit+0x82
linker_file_sysinit(c5920d00,c5e4d460,e4f4cc24,1,c5920d00) at linker_file_sysini
t+0x8e
linker_load_file(c5e4d460,e4f4cc48,0,c106ca00,0) at linker_load_file+0xed
linker_load_module(0,c4bc3c00,0,0,e4f4cc74) at linker_load_module+0xb1
kldload(c4a14d80,e4f4cd04,4,280d5000,4) at kldload+0x139
syscall(3b,3b,3b,bfbfead0,bfbfeab8) at syscall+0x386
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (304, FreeBSD ELF32, kldload), eip = 0x280d54ef, esp = 0xbfbfe4cc, e
bp = 0xbfbfea88 ---
netsmb_dev: loaded
lockmgr: thread 0xc5298bd0 unlocking unheld lock
KDB: stack backtrace:
kdb_backtrace(c06a0a0b,c5298bd0,c4a5781c,c6741840,c6742880) at kdb_backtrace+0x2
f
lockmgr(c5a49408,6,c5a4942c,c5298bd0,e7257ba0) at lockmgr+0x604
smb_co_unlock(c5a49400,0,c5298bd0,e7257bfc,c6bef43a) at smb_co_unlock+0x2c
smb_vc_unlock(c5a49400,0,c5298bd0,e7257bc0,c51e7800) at smb_vc_unlock+0x1f
nsmb_dev_ioctl(c5913d00,82fc6e6a,c4a57800,3,c5298bd0) at nsmb_dev_ioctl+0x3d4
giant_ioctl(c5913d00,82fc6e6a,c4a57800,3,c5298bd0) at giant_ioctl+0x79
devfs_ioctl_f(c4c365a0,82fc6e6a,c4a57800,c58b4d00,c5298bd0) at devfs_ioctl_f+0xd
c
ioctl(c5298bd0,e7257d04,c,2817f000,6) at ioctl+0x537
syscall(3b,3b,3b,bfbfe6c0,bfbfe1a0) at syscall+0x386
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (54, FreeBSD ELF32, ioctl), eip = 0x2816a277, esp = 0xbfbfe18c, ebp 
= 0xbfbfe4b8 ---
lockmgr: thread 0xc5298bd0 unlocking unheld lock
KDB: stack backtrace:
kdb_backtrace(c06a0a0b,c5298bd0,c4a5781c,c6741840,c6742880) at kdb_backtrace+0x2
f
lockmgr(c576e308,6,c576e32c,c5298bd0,e7257ba0) at lockmgr+0x604
smb_co_unlock(c576e300,0,c5298bd0,e7257bfc,c6bef46c) at smb_co_unlock+0x2c
smb_share_unlock(c576e300,0,c5298bd0,e7257bc0,c51e7800) at smb_share_unlock+0x1f
nsmb_dev_ioctl(c5913d00,82fc6e6a,c4a57800,3,c5298bd0) at nsmb_dev_ioctl+0x406
giant_ioctl(c5913d00,82fc6e6a,c4a57800,3,c5298bd0) at giant_ioctl+0x79
devfs_ioctl_f(c4c365a0,82fc6e6a,c4a57800,c58b4d00,c5298bd0) at devfs_ioctl_f+0xd
c
ioctl(c5298bd0,e7257d04,c,2817f000,6) at ioctl+0x537
syscall(3b,3b,3b,bfbfe6c0,bfbfe1a0) at syscall+0x386
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (54, FreeBSD ELF32, ioctl), eip = 0x2816a277, esp = 0xbfbfe18c, ebp 
= 0xbfbfe4b8 ---

is it a known problem?
this happens on UP and SMP systems, both running recent CURRENT.

bye
-- 

Paolo

Piso's first law: nothing works as expected!