Re: VOP_PRINT: 0xc775b128 interlock is locked but should not be

From: Alexander Kabaev <ak03_at_gte.com>
Date: Sat, 3 Jan 2004 23:13:06 -0500

ffs_snapshot calls vprint with vnode interlock held and that triggers
DEBUG_VFS_LOCKS guards on VOP_PRINT. You have both snapdebug and vfs
locking debugging enabled in your kernel?

I moved vprint lower in the function for now.

-- 
Alexander Kabaev

Received on Sat Jan 03 2004 - 19:13:13 UTC

This message: [ Message body ]
Next message: Dejan Lesjak: "Re: 5.2-RC oerrs and collisions on dc0"
Previous message: Doug White: "Re: Have 5.2-RC2 and still getting "ACPI-1287: *** Error" messages"
In reply to: Jun Kuriyama: "VOP_PRINT: 0xc775b128 interlock is locked but should not be"
Next in thread: Jun Kuriyama: "Re: VOP_PRINT: 0xc775b128 interlock is locked but should not be"
Reply: Jun Kuriyama: "Re: VOP_PRINT: 0xc775b128 interlock is locked but should not be"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:36 UTC