Date: Tue, 5 Mar 2019 00:29:09 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Nick Rogers <ncrogers@gmail.com> Cc: FreeBSD STABLE <freebsd-stable@freebsd.org> Subject: Re: 12.0-RELEASE zfs/vnode deadlock issue Message-ID: <ebf49f31-7b9a-815e-3d04-aa44533f57ba@FreeBSD.org> In-Reply-To: <CAKOb=YYkuH=8Q94wi=q_zB%2BMS%2BNWXr5Q3_VRarYS5zTz%2BSPfUw@mail.gmail.com> References: <CAKOb=YaLSPPRrLWGPbcDt0tKqS2h3mT2dLo92aK3r-8O%2B3SHTw@mail.gmail.com> <233f3723-a78e-91db-ebe6-9e13c1c9b50d@FreeBSD.org> <CAKOb=YYkuH=8Q94wi=q_zB%2BMS%2BNWXr5Q3_VRarYS5zTz%2BSPfUw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/03/2019 22:35, Nick Rogers wrote:
> v_lock = {lock_object = {lo_name =
> 0xffffffff8144af45 "zfs", lo_flags = 117112840, lo_data = 0, lo_witness =
> 0x0}, lk_lock = 18446744073709551605, lk_exslpfail = 0, lk_timo = 51,
> lk_pri = 96}
Hmm, lk_lock looks bogus.
18446744073709551605 == 0xfffffffffffffff5 and it's LK_SHARE |
LK_EXCLUSIVE_WAITERS with 0xfffffffffffffff shared owners.
Perhaps, this is a result of LK_SHARERS_LOCK(-1).
Is your kernel compiled with INVARIANTS and INVARIANT_SUPPORT?
I suspect that the vnode was accessed (unlocked?) through a stale pointer after
it was recycled.
--
Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ebf49f31-7b9a-815e-3d04-aa44533f57ba>