Date: Wed, 27 Sep 2006 16:01:45 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: current@freebsd.org Subject: "recursive lock for object" & "unlocking unheld lock" in smb Message-ID: <20060927160145.vl5ls2dz44ccscwo@webmail.leidinger.net>
next in thread | raw e-mail | index | archive | help
Hi,
yesterday I rsynced a smb share from a samba-3.0.x server (FreeBSD 4) =20
via a smb mount (current from Sep 23) "locally" (mount -t smbfs from =20
the samba server and rsync a/ b/; most easy solution to convert some =20
ISO-8859-1 filenames to UTF-8 ("dos charset =3D UTF8" in smb.conf!) =20
while moving to another system).
Today I noticed the following in the daily mail on the -current system:
+++ /tmp/security.w9S5FGBa=09Wed Sep 27 03:02:41 2006
+netsmb_dev: loaded
+smb_co_lock: recursive lock for object 1
+lockmgr: thread 0xc3d6fbd0 unlocking unheld lock
+KDB: stack backtrace:
+lockmgr(c79a9c08,2006,c79a9c2c,c3d6fbd0,e5a38b9c,...) at lockmgr+0x529
+smb_co_put(c79a9c00,e5a38b9c,c3d6fbd0,c34a7c00,c79a9c00,...) at =20
smb_co_put+0x6e
+smb_sm_lookup(e5a38b28,e5a38b08,e5a38b9c,e5a38b04,c3654a00,...) at =20
smb_sm_lookup+0x10d
+smb_usr_lookup(c32cb800,e5a38b9c,e5a38b98,e5a38b94,0,...) at =20
smb_usr_lookup+0x6c
+nsmb_dev_ioctl(c3d65200,82fc6e6a,c32cb800,3,c3d6fbd0) at nsmb_dev_ioctl+0x2=
d5
+giant_ioctl(c3d65200,82fc6e6a,c32cb800,3,c3d6fbd0,...) at giant_ioctl+0x51
+devfs_ioctl_f(c3b57558,82fc6e6a,c32cb800,c3e36a80,c3d6fbd0) at =20
devfs_ioctl_f+0x9d
+kern_ioctl(c3d6fbd0,3,82fc6e6a,c32cb800) at kern_ioctl+0x286
+ioctl(c3d6fbd0) at ioctl+0xca
+syscall(3b,3b,3b,bfbfe91c,bfbfe444,...) at syscall+0x28f
+Xint0x80_syscall() at Xint0x80_syscall+0x1f
+--- syscall (54, FreeBSD ELF32, ioctl), eip =3D 0x28138e43, esp =3D =20
0xbfbfe434, ebp =3D 0xbfbfe750 ---
+smb_co_lock: recursive lock for object 1
+lockmgr: thread 0xc3aa8870 unlocking unheld lock
+KDB: stack backtrace:
+lockmgr(c449dc08,2006,c449dc2c,c3aa8870,e59edb9c,...) at lockmgr+0x529
+smb_co_put(c449dc00,e59edb9c,c3aa8870,c7499700,c449dc00,...) at =20
smb_co_put+0x6e
+smb_sm_lookup(e59edb28,e59edb08,e59edb9c,e59edb04,c3654a00,...) at =20
smb_sm_lookup+0x10d
+smb_usr_lookup(c30cc800,e59edb9c,e59edb98,e59edb94,0,...) at =20
smb_usr_lookup+0x6c
+nsmb_dev_ioctl(c76b4100,82fc6e6a,c30cc800,3,c3aa8870) at nsmb_dev_ioctl+0x2=
d5
+giant_ioctl(c76b4100,82fc6e6a,c30cc800,3,c3aa8870,...) at giant_ioctl+0x51
+devfs_ioctl_f(c44d6360,82fc6e6a,c30cc800,c3e36a80,c3aa8870) at =20
devfs_ioctl_f+0x9d
+kern_ioctl(c3aa8870,3,82fc6e6a,c30cc800) at kern_ioctl+0x286
+ioctl(c3aa8870) at ioctl+0xca
+syscall(bfbf003b,bfbf003b,e59e003b,bfbfe91c,bfbfe444,...) at syscall+0x28f
+Xint0x80_syscall() at Xint0x80_syscall+0x1f
+--- syscall (54, FreeBSD ELF32, ioctl), eip =3D 0x28138e43, esp =3D =20
0xbfbfe434, ebp =3D 0xbfbfe750 ---
To reproduce this it should be enough to setup samba, export something =20
from it and mount it somewhere on a FreeBSD system. I had one file =20
which was not owned by the user I used to authenticate to the samba =20
server and this file was not readable by enyone except the owner =20
itself (root). I tried to rsync twice before having a look at the file =20
at the source system. Maybe this is needed to reproduce this.
Bye,
Alexander.
--=20
Out of the crooked timber of humanity no straight thing can ever be made.
=09=09-- Immanuel Kant
http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060927160145.vl5ls2dz44ccscwo>