From owner-freebsd-current@FreeBSD.ORG Mon Mar 16 18:29:41 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 C7CCC10656C8 for ; Mon, 16 Mar 2009 18:29:41 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-bw0-f164.google.com (mail-bw0-f164.google.com [209.85.218.164]) by mx1.freebsd.org (Postfix) with ESMTP id 29DBF8FC1B for ; Mon, 16 Mar 2009 18:29:40 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by bwz8 with SMTP id 8so3503012bwz.43 for ; Mon, 16 Mar 2009 11:29:40 -0700 (PDT) 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:content-type:content-transfer-encoding; bh=PLmLdWxIhGzJRUu/W6Ed6v1iGlv4RQjFRRDcFL8gTHU=; b=LMGZEBnz1AZgVmVm1f3pjmVBhVSzvIT/zVqKVqaHfbG5Sb2SGuLxFI1Za5GMMT+pdY LUJUsaIPtB1KHNTLgwBVR+YNQi2cS39/yPKKDGUJahc50SGZRCXu3Dtjj8bvDBwSDkVD rIxPgWax+qkt2A9j+6JAnW18koKCMLTHCRIGc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=bQTya1QyfKEX2FoAC2pDdVLCnI8ArQwAbl1NwoXC9NXJKAuKj98FIb2bRX3OfnbTYa R9lBORyULtP19uIdTwVViq+RZ/debf8aSJEyBvr0LEewAQ/L3mVwGecO8Z716xTSvZGv +Lxm272fFJ6tFmXY/FWc3MwUT5zSsnuBGxTls= MIME-Version: 1.0 Received: by 10.86.100.16 with SMTP id x16mr1200979fgb.68.1237228179878; Mon, 16 Mar 2009 11:29:39 -0700 (PDT) Date: Mon, 16 Mar 2009 21:29:39 +0300 Message-ID: From: pluknet To: FreeBSD-Current Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: LOR 1) proctree 2) ufs 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, 16 Mar 2009 18:29:43 -0000 Hello. A yet another of the numerous fs witness warns. This one seems not to be reported anywhere else yet. It's triggered with ktrace, certainly. lock order reversal: 1st 0xc08bbf30 proctree (proctree) @ /usr/src/sys/kern/kern_ktrace.c:718 2nd 0xc672fc70 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2205 KDB: stack backtrace: db_trace_self_wrapper(c08292a7,e80279cc,c0604035,c05f5c2b,c082c14d,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c05f5c2b,c082c14d,c54ef068,c54f6978,e8027a28,...) at kdb_backtrace+0x29 _witness_debugger(c082c14d,c672fc70,c081f7ec,c54f6978,c0832f2c,...) at _witness_debugger+0x25 witness_checkorder(c672fc70,9,c0832f2c,89d,0,...) at witness_checkorder+0x839 __lockmgr_args(c672fc70,80100,c672fcd8,0,0,...) at __lockmgr_args+0x7a7 ffs_lock(e8027b34,c0603ddb,c0832f2c,80100,c672fc18,...) at ffs_lock+0xa1 VOP_LOCK1_APV(c088e5e0,e8027b34,c05b5da3,c08a3d60,c672fc18,...) at VOP_LOCK1_APV+0xb5 _vn_lock(c672fc18,80100,c0832f2c,89d,4,...) at _vn_lock+0x78 vrele(c672fc18,0,c0822999,36b,c5b1e5d0,...) at vrele+0x15a ktrops(1fe,0,c0822999,384,1,...) at ktrops+0x28d ktrsetchildren(1fe,0,c0822999,300,0,...) at ktrsetchildren+0x5c ktrace(c60f3690,e8027cf8,10,c082d384,c0871298,...) at ktrace+0x622 syscall(e8027d38) at syscall+0x2b4 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (45, FreeBSD ELF32, ktrace), eip = 0x280d11cf, esp = 0xbfbfecbc, ebp = 0xbfbfed68 --- -- wbr, pluknet