Re: panic: fsync: vnode is not exclusive locked but should be

Reply: Alexander Leidinger : "Re: panic: fsync: vnode is not exclusive locked but should be"
In reply to: Alexander Leidinger : "panic: fsync: vnode is not exclusive locked but should be"
Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Konstantin Belousov <kostikbel_at_gmail.com>
Date: Mon, 04 Aug 2025 20:14:59 UTC

On Mon, Aug 04, 2025 at 08:50:45PM +0200, Alexander Leidinger wrote:
> Hi,
> 
> I have a crash with todays -current:
> ---snip---
> [435] VNASSERT failed: locked not true at
> /space/system/usr_src/sys/kern/vfs_subr.c:5795 (assert_vop_elocked)
> [435] 0xfffff806746f2000: type VREG state VSTATE_CONSTRUCTED op
> 0xffffffff835474f8
> [435]     usecount 1, writecount 1, refcount 1 seqc users 0
> [435]     hold count flags ()
> [435]     flags ()
> [435]     v_object 0xfffff80bd3abf0f8 ref 0 pages 0 cleanbuf 0 dirtybuf 0
> [435]     lock type zfs: SHARED (count 1)
> [435]   vp=0xfffff806746f2000, lowervp=0xfffff806749bd370
> [435] panic: fsync: vnode is not exclusive locked but should be

This is nullfs over zfs.  Try https://reviews.freebsd.org/D51730.
It should fix the issue, but I did not tested.