Date: Tue, 26 Mar 2002 14:43:07 -0800 From: Alfred Perlstein <alfred@FreeBSD.org> To: Kris Kennaway <kris@obsecurity.org> Cc: current@FreeBSD.org Subject: Re: Lock order reversals in sys_pipe.c Message-ID: <20020326224307.GE93885@elvis.mu.org> In-Reply-To: <20020324142632.A60767@xor.obsecurity.org> References: <20020324142632.A60767@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Kris Kennaway <kris@obsecurity.org> [020324 14:26] wrote: > The bento cluster is now running with WITNESS enabled to try and track > down some odd UMA lock corruption panics. Instead, it found the > following lock order reversal in sys_pipe.c overnight: > > Mar 24 07:31:44 <user.crit> gohan17 kernel: lock order reversal > Mar 24 07:31:44 <user.crit> gohan17 kernel: 1st 0xcf51aa80 pipe mutex @ /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 > Mar 24 07:31:44 <user.crit> gohan17 kernel: 2nd 0xcf88dadc process lock @ /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 > Mar 24 07:32:12 <user.crit> gohan10 kernel: lock order reversal > Mar 24 07:32:12 <user.crit> gohan10 kernel: 1st 0xd9a29dc0 pipe mutex @ /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 > Mar 24 07:32:12 <user.crit> gohan10 kernel: 2nd 0xd961addc process lock @ /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 > Mar 24 07:32:57 <user.crit> gohan12 kernel: lock order reversal > Mar 24 07:32:57 <user.crit> gohan12 kernel: 1st 0xd9423080 pipe mutex @ /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 > Mar 24 07:32:57 <user.crit> gohan12 kernel: 2nd 0xdaa704dc process lock @ /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 > Mar 24 09:02:29 <user.crit> gohan13 kernel: lock order reversal > Mar 24 09:02:29 <user.crit> gohan13 kernel: 1st 0xd99d6500 pipe mutex @ /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 > Mar 24 09:02:29 <user.crit> gohan13 kernel: 2nd 0xd971cddc process lock @ /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 > > Those source references are from a -current kernel from last night. Are you %100 on that? How did you get this to happen? I can see where I hold the pipe lock, then try to get a proc lock, but not the other way around... Any ideas? -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020326224307.GE93885>