Date: Sat, 25 Jun 2005 15:12:57 +0400 From: Sergey Zaharchenko <doublef-ctm@yandex.ru> To: freebsd-current@freebsd.org Subject: unionfs renaming panic Message-ID: <20050625111257.GA1826@shark.localdomain>
next in thread | raw e-mail | index | archive | help
--uAKRQypu60I7Lcqm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hello list,
I believe I have found a panic with renaming files on a unionfs.
Here's a script to reproduce it (assuming you have booted in
single-user).
# mount -u /
# mkdir /mnt2
# mount_unionfs /mnt2 /mnt
# cd /mnt
# echo Hello >foo
# mv foo bar
The part of the backtrace before the debugger is:
#23 0xc064557b in kdb_enter (msg=3D0x0) at cpufunc.h:60
#24 0xc062d997 in panic (fmt=3D0xc084d6bc "lockmgr: locking against myself")
at /static/srcfs/usr.src/sys/kern/kern_shutdown.c:537
#25 0xc0622f12 in lockmgr (lkp=3D0xc1525058, flags=3D12290, interlkp=3D0x80,
td=3D0xc13fb900) at /static/srcfs/usr.src/sys/kern/kern_lock.c:329
#26 0xc0678f9a in vop_stdlock (ap=3D0x0)
at /static/srcfs/usr.src/sys/kern/vfs_default.c:258
#27 0xc07f7fe3 in VOP_LOCK_APV (vop=3D0xc08bbcc0, a=3D0xcbfd7ad0)
at vnode_if.c:1642
#28 0xc068bc90 in vn_lock (vp=3D0xc1525000, flags=3D4098, td=3D0xc13fb900)
at vnode_if.h:844
#29 0xc067a9c6 in lookup (ndp=3D0xcbfd7c18)
at /static/srcfs/usr.src/sys/kern/vfs_lookup.c:380
#30 0xc067a696 in namei (ndp=3D0xcbfd7c18)
at /static/srcfs/usr.src/sys/kern/vfs_lookup.c:201
#31 0xc06880a4 in kern_rename (td=3D0xc13fb900, from=3D0x0, to=3D0x0, paths=
eg=3DUIO_USERSPACE)
^^^^^^^^^^^^^^^^
is this
at /static/srcfs/usr.src/sys/kern/vfs_syscalls.c:3221
#32 0xc0687fad in rename (td=3D0xc13fb900, uap=3D0x0)
^^^^^^^^
and this OK?
at /static/srcfs/usr.src/sys/kern/vfs_syscalls.c:3177
#33 0xc07e834b in syscall (frame=3D
{tf_fs =3D 59, tf_es =3D 59, tf_ds =3D 59, tf_edi =3D -1077940477, tf=
_esi =3D -1077940473, tf_ebp =3D -1077941896, tf_isp =3D -872579740, tf_ebx=
=3D 0, tf_edx =3D -1, tf_ecx =3D 2, tf_eax =3D 128, tf_trapno =3D 12, tf_e=
rr =3D 2, tf_eip =3D 671866095, tf_cs =3D 51, tf_eflags =3D 646, tf_esp =3D=
-1077943572, tf_ss =3D 59})
at /static/srcfs/usr.src/sys/i386/i386/trap.c:976
#34 0xc07d573f in Xint0x80_syscall ()
at /static/srcfs/usr.src/sys/i386/i386/exception.s:200
Relevant Id's:
# ident kernel.debug |grep vfs_syscalls.c
$FreeBSD: src/sys/kern/vfs_syscalls.c,v 1.391 2005/06/14 01:14:40 jeff=
Exp $
# ident kernel.debug |grep vfs_lookup.c
$FreeBSD: src/sys/kern/vfs_lookup.c,v 1.80 2005/04/13 23:36:28 jeff Ex=
p $
Kernel/world built from the 6898'th CTM delta.
Moving from unionfs to a normal fs also results in a panic (the
backtrace seems to be different, but I don't have it at the moment).
Moving from normal fs to unionfs works OK.
Ideas?
--=20
DoubleF
make(1) to rule them all, grep(1) to find them,
patch(1) to fix them all and cvs ci them.
--uAKRQypu60I7Lcqm
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)
iD8DBQFCvTw5wo7hT/9lVdwRAl9zAJ9582QgxQbeEs4Ml5pL85GTLl9OWgCeM04N
Y/gyxldTR4+OhjQmWe/DkKY=
=pyG/
-----END PGP SIGNATURE-----
--uAKRQypu60I7Lcqm--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050625111257.GA1826>