From owner-freebsd-i386@freebsd.org Wed Jun 29 07:00:47 2016 Return-Path: Delivered-To: freebsd-i386@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D81F6B86C39 for ; Wed, 29 Jun 2016 07:00:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BD1712AE0 for ; Wed, 29 Jun 2016 07:00:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5T70l9P022629 for ; Wed, 29 Jun 2016 07:00:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-i386@FreeBSD.org Subject: [Bug 210684] LOR between so_snd_sx and ufs Date: Wed, 29 Jun 2016 07:00:47 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ml@netfence.it X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 07:00:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210684 Bug ID: 210684 Summary: LOR between so_snd_sx and ufs Product: Base System Version: 10.3-RELEASE Hardware: i386 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: ml@netfence.it CC: freebsd-i386@FreeBSD.org CC: freebsd-i386@FreeBSD.org For reasons beyond the scope, I compiled a kernel with debug checks and got: Jun 29 07:46:38 xxxxxx kernel: Starting winbindd. Jun 29 07:46:38 xxxxxx winbindd[781]: [2016/06/29 07:46:38.915443, 0] ../source3/winbindd/winbindd_cache.c:3245(initialize_winbindd_cache) Jun 29 07:46:38 xxxxxx kernel: Starting snmpd. Jun 29 07:46:38 xxxxxx kernel: Jun 29 07:46:38 xxxxxx winbindd[781]: [2016/06/29 07:46:38.915443, 0] ../source3/winbindd/winbindd_cache.c:3245(initialize_winbindd_cache) Jun 29 07:46:38 xxxxxx winbindd[781]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Jun 29 07:46:38 xxxxxx kernel: Jun 29 07:46:38 xxxxxx winbindd[781]:=20=20 initialize_winbindd_cache: clearing cache and re-creating with version numb= er 2 Jun 29 07:46:39 xxxxxx winbindd[781]: [2016/06/29 07:46:39.197239, 0] ../lib/util/become_daemon.c:124(daemon_ready) Jun 29 07:46:39 xxxxxx kernel: Jun 29 07:46:39 xxxxxx winbindd[781]: [2016/06/29 07:46:39.197239, 0] ../lib/util/become_daemon.c:124(daemon_rea= dy) Jun 29 07:46:39 xxxxxx winbindd[781]: STATUS=3Ddaemon 'winbindd' finished starting up and ready to serve connections Jun 29 07:46:39 xxxxxx kernel: Jun 29 07:46:39 xxxxxx winbindd[781]:=20=20 STATUS=3Ddaemon 'winbindd' finished starting up and ready to serve connecti= ons Jun 29 07:46:40 xxxxxx kernel: lock order reversal: Jun 29 07:46:40 xxxxxx kernel: 1st 0xce58eb14 so_snd_sx (so_snd_sx) @ /usr/src/sys/kern/uipc_sockbuf.c:148 Jun 29 07:46:40 xxxxxx kernel: 2nd 0xce2b0150 ufs (ufs) @ /usr/src/sys/kern/vfs_lookup.c:509 Jun 29 07:46:40 xxxxxx kernel: KDB: stack backtrace: Jun 29 07:46:40 xxxxxx kernel: db_trace_self_wrapper(c0a1efd8,3834313a,ce2a000a,ce2af838,a1,...) at db_trace_self_wrapper+0x2d/frame 0xf853c4f8 Jun 29 07:46:40 xxxxxx kernel: kdb_backtrace(c0a231d4,ce2b0150,c0a0ed4d,cd7bfb08,c0a2be9c,...) at kdb_backtrace+0x30/frame 0xf853c55c Jun 29 07:46:40 xxxxxx kernel: witness_checkorder(ce2b0150,1,c0a2be9c,1fd,0,...) at witness_checkorder+0xd4f/frame 0xf853c5a8 Jun 29 07:46:40 xxxxxx kernel: __lockmgr_args(ce2b0150,202400,ce2b0170,0,0,= ...) at __lockmgr_args+0x4b8/frame 0xf853c688 Jun 29 07:46:40 xxxxxx kernel: ffs_lock(f853c708,c0b7fcf0,c0cab8b8,c0aa6708,cd7b6248,...) at ffs_lock+0x94/frame 0xf853c6c4 Jun 29 07:46:40 xxxxxx kernel: VOP_LOCK1_APV(c0abc8f0,f853c708,200246,9cb,c0ad43f8,...) at VOP_LOCK1_APV+0x10a/frame 0xf853c6f0 Jun 29 07:46:40 xxxxxx kernel: _vn_lock(ce2b011c,202400,c0a2be9c,1fd,0,...)= at _vn_lock+0xca/frame 0xf853c730 Jun 29 07:46:40 xxxxxx kernel: lookup(f853c888,c0a2be9c,110,d5,ce34a280,...= ) at lookup+0xf5/frame 0xf853c790 Jun 29 07:46:40 xxxxxx kernel: namei(f853c888,0,144,1,f853c929,...) at namei+0x48d/frame 0xf853c828 Jun 29 07:46:40 xxxxxx kernel: unp_connectat(ce270300,cde9f960,c0a29331,364,f853cb50,...) at unp_connectat+0x1e9/frame 0xf853ca3c Jun 29 07:46:40 xxxxxx kernel: uipc_send(ce58e9f0,0,ce877700,ce270300,0,...= ) at uipc_send+0x5a1/frame 0xf853ca90 Jun 29 07:46:40 xxxxxx kernel: sosend_generic(ce58e9f0,ce270300,f853cb50,0,0,...) at sosend_generic+0x3c9/frame 0xf853cb08 Jun 29 07:46:40 xxxxxx kernel: kern_sendit(cde9f960,6,f853cbe8,0,0,...) at kern_sendit+0x207/frame 0xf853cb88 Jun 29 07:46:40 xxxxxx kernel: sendit(f853cbe8,0,f853cbe4,28,ce1a6918,...) = at sendit+0x11d/frame 0xf853cbc8 Jun 29 07:46:40 xxxxxx kernel: sys_sendmsg(cde9f960,f853cca8,ce1a6918,f853cc70,c098ee18,...) at sys_sendmsg+0x79/frame 0xf853cc18 Jun 29 07:46:40 xxxxxx kernel: syscall(f853cce8) at syscall+0x381/frame 0xf853ccdc Jun 29 07:46:40 xxxxxx kernel: Xint0x80_syscall() at Xint0x80_syscall+0x2f/frame 0xf853ccdc Jun 29 07:46:40 xxxxxx kernel: --- syscall (28, FreeBSD ELF32, sys_sendmsg), eip =3D 0x22867abf, esp =3D 0xbfbfc688, ebp =3D 0xbfbfc6a4 --- Jun 29 07:46:41 xxxxxx kernel: Starting smartd. The box did not panic or enter the debugger, so I'm not sure how severe is this, but AFAICT it hasn't been reported yet. In case it matters, the box is an NFS client with two GMIRRORed SCSI disks. --=20 You are receiving this mail because: You are on the CC list for the bug.=