Re: Where to report LORs? (ffs and unionfs LORs included

From: Bjoern A. Zeeb <bzeeb-lists_at_lists.zabbadoz.net>
Date: Wed, 14 Oct 2009 06:37:57 +0000 (UTC)
On Tue, 13 Oct 2009, Alexander Best wrote:

> Harald Schmalzbauer schrieb am 2009-10-10:
>> Alexander Best schrieb am 07.07.2009 21:33 (localtime):
>>> try http://sources.zabbadoz.net/freebsd/lor.html
>
>> I still see a unionfs LOR with RELENG_8 which is not listed, so I'd
>> like to report it again.
>> lock order reversal:
>> 1st 0xc372c488 unionfs (unionfs) _at_
>> /FlashBSD/src/sys/fs/unionfs/union_subr.c:356
>> 2nd 0xc372c594 ufs (ufs) _at_ /FlashBSD/src/sys/kern/vfs_subr.c:2188
>> KDB: stack backtrace:
>> db_trace_self_wrapper(c0616390,c08cd5d5,c3416770,c3416500,d5c42864,..
>> .) at db_trace_self_wrapper+0x26
>> _witness_debugger(c08cd5d5,c372c594,c08c0703,c3416500,c08d4ec2,...)
>> at _witness_debugger+0x49
>> witness_checkorder(c372c594,9,c08d4ec2,88c,0,...) at
>> witness_checkorder+0x6ec
>> __lockmgr_args(c372c594,80100,c372c5b0,0,0,...) at
>> __lockmgr_args+0xc97
>> ffs_lock(d5c42958,8,c36c4764,80100,c372c53c,...) at ffs_lock+0x96
>> VOP_LOCK1_APV(c09374a0,d5c42958,c05d89e9,c09477c0,c372c53c,...) at
>> VOP_LOCK1_APV+0x9a
>> _vn_lock(c372c53c,80100,c08d4ec2,88c,c0877c6e,...) at _vn_lock+0x46
>> vrele(c372c53c,d5c429d8,c372c4a4,0,0,...) at vrele+0x12a
>> unionfs_noderem(c372c430,c36c46c0,d5c42a44,c06764fc,d5c42a20,...) at
>> unionfs_noderem+0x1e5
>> unionfs_reclaim(d5c42a20,d5c42a20,0,0,c372c4a4,...) at
>> unionfs_reclaim+0x1b
>> vgonel(c372c4a4,0,c08d4ec2,9c5,c372c4a4,...) at vgonel+0x100
>> vrecycle(c372c430,c36c46c0,d5c42aa4,c0675c29,d5c42a8c,...) at
>> vrecycle+0x6a
>> unionfs_inactive(d5c42a8c,d5c42a8c,c08d4ec2,924,c0947780,...) at
>> unionfs_inactive+0x28
>> vinactive(c372c594,d5c42ac0,c08d4ec2,8aa,c3451de0,...) at
>> vinactive+0x6a
>> vput(c372c430,ffffffdf,c344ab80,0,c36c46c0,...) at vput+0x205
>> kern_statat_vnhook(c36c46c0,0,ffffff9c,28209e1c,0,...) at
>> kern_statat_vnhook+0xe0
>> kern_statat(c36c46c0,0,ffffff9c,28209e1c,0,...) at kern_statat+0x3c
>> kern_stat(c36c46c0,28209e1c,0,d5c42c18,c0a83a18,...) at
>> kern_stat+0x36
>> stat(c36c46c0,d5c42cf8,8,d5c42d38,c0916cd0,...) at stat+0x2b
>> syscall(d5c42d38) at syscall+0x176
>> Xint0x80_syscall() at Xint0x80_syscall+0x20
>> --- syscall (188, FreeBSD ELF32, stat), eip = 0x281c6c2b, esp =
>> 0xbfbfe96c, ebp = 0xbfbfea68 ---
>
>> So far I couldn't notice any deadlock, but the box is not in
>> production yet.
>
>> -Harry
>
> you might also want to write Bjoern Zeeb (http://wiki.freebsd.org/BjoernZeeb)
> with a link to your report. he's the guy maintaining the lor page.

preferably use the reference already give in this thread at the top:
http://sources.zabbadoz.net/freebsd/lor.html

/bz

-- 
Bjoern A. Zeeb         It will not break if you know what you are doing.
Received on Wed Oct 14 2009 - 04:40:09 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:56 UTC