From owner-freebsd-current@FreeBSD.ORG Mon Nov 23 09:17:26 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD51E1065676 for ; Mon, 23 Nov 2009 09:17:26 +0000 (UTC) (envelope-from sahil.cooner@gmail.com) Received: from mail-pz0-f185.google.com (mail-pz0-f185.google.com [209.85.222.185]) by mx1.freebsd.org (Postfix) with ESMTP id B43858FC1E for ; Mon, 23 Nov 2009 09:17:26 +0000 (UTC) Received: by pzk15 with SMTP id 15so3640071pzk.3 for ; Mon, 23 Nov 2009 01:17:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=qtplkEPdUERJJmq9BeHdGhhEfCoxUWCu4bkeqx2t20A=; b=bsNFRV8MNhVnZdselDyva6xqTW8RGJSnknqN07ECXiKAZWqdnrdM7riuV2ZWlPaM4Z kvxrZs8DJjMUFe2rcwkkZNdXnJs1aRucKcZ0KyHfryuAnvVNXl5jw1nQv8cpK2SfGrWW zHwf75yLvnnLg5fJ2b36Sgz2rQQ4IHlyFEBzI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=Pwv8ITFla90uRqazp4mLFs+/1vvf/Xx6CmnNnQkV7hkz00gvnut9bw9iFMmuyUW8zp La6A9AhFAJJ0+2dZvGTLpV/N+e5/kDLgB9j7Vf8GXbxmwKC0WUJfyjJ6DDa8vYljKTb4 TQ3dUOzxlKTVZSMP75COZIsnZMMb4KCsVs9IM= MIME-Version: 1.0 Received: by 10.141.1.19 with SMTP id d19mr29800rvi.262.1258966483053; Mon, 23 Nov 2009 00:54:43 -0800 (PST) Date: Mon, 23 Nov 2009 02:54:43 -0600 Message-ID: From: "sahil.cooner@gmail.com" To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: bzeeb+freebsd+lor@zabbadoz.net Subject: mount_smbfs lock order traversal kernel segfault X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2009 09:17:26 -0000 Fellow FreeBSDers, I'd like to report a new lock order traversal bug that I have come across in freebsd-current, from a checkout of the /usr/src tree a couple days ago. I found the following site and search for the particular LOR dump that I was receiving in dmesg. I am currently receiving 2 different LOR errors. One that is a known and reported issue, the other I could not find on the following list, http://sources.zabbadoz.net/freebsd/lor.html. Following these instructions ... http://sources.zabbadoz.net/freebsd/lor.html#howtoreportalor 1) The Backtrace... smb_co_lock: recursive lock for object 1 lock order reversal: 1st 0xffffff0020401c08 smb_vc (smb_vc) @ /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:331 2nd 0xffffffff812c84a8 smbsm (smbsm) @ /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:354 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e __lockmgr_args() at __lockmgr_args+0xcf3 smb_co_lock() at smb_co_lock+0x61 smb_co_gone() at smb_co_gone+0x34 smb_sm_lookup() at smb_sm_lookup+0x105 smb_usr_lookup() at smb_usr_lookup+0xcd nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1e7 giant_ioctl() at giant_ioctl+0x75 devfs_ioctl_f() at devfs_ioctl_f+0x76 kern_ioctl() at kern_ioctl+0xc5 ioctl() at ioctl+0xfd syscall() at syscall+0x1ae Xfast_syscall() at Xfast_syscall+0xe1 --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x80094b92c, rsp = 0x7fffffffe128, rbp = 0x7fffffffe540 --- 2) The Samba server is a Debian box running Samba versions as follows... smbd -V Version 3.2.5 nmbd -V Version 3.2.5 3) uname -arv FreeBSD mybox.com 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Sat Nov 21 07:47:20 CST 2009 root@mybox.com:/usr/obj/usr/src/sys/GENERIC amd64 This bug is almost always reproducible when any sort of slightly higher than normal disk I/O takes place to the samba mounted directory, ie. a copy from the remote target to the local drive of a 1GB file. I haven't really had a chance to follow up by looking through the relevant /usr/src/sys/../../smbfs/../*.c files to try and debug/determine some more information I will respond with relevant follow ups. Cheers, Sahil R Cooner Pablo Picasso - "Computers are useless. They can only give you answers."