From nobody Fri Jul 02 12:01:47 2021 X-Original-To: bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 8F70E11E3B30 for ; Fri, 2 Jul 2021 12:01:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GGYbH3YyMz4SG2 for ; Fri, 2 Jul 2021 12:01:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 6352213ACB for ; Fri, 2 Jul 2021 12:01:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 162C1lOS049742 for ; Fri, 2 Jul 2021 12:01:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 162C1lgu049741 for bugs@FreeBSD.org; Fri, 2 Jul 2021 12:01:47 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 256937] Kernel panic on FUSE filesystem - lockmgr_xlock_hard: recursing on non recursive lockmgr Date: Fri, 02 Jul 2021 12:01:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: chogata@moosefs.pro X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256937 Bug ID: 256937 Summary: Kernel panic on FUSE filesystem - lockmgr_xlock_hard: recursing on non recursive lockmgr Product: Base System Version: 13.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: chogata@moosefs.pro Created attachment 226169 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D226169&action= =3Dedit Kernel panic backtrace message The problem is repeatedly spotted on a machine with FreeBSD 13.0 running MooseFS client that uses FUSE. The machine crashes daily, I'm attaching a screenshot of panic backtrace. It was reported to MooseFS team by a user an= d we promised to help investigate the problem. From the fact, that this FreeBSD machine logs repeatedly: "fuse_internal_do_getattr: cache incoherent on [PATH]! Buggy FUSE server detected" and the backtrace that shows an attempt at write and then invokes "fuse_internal_do_getattr", we suspect that the kernel panics when it gets a different length than it has in its internal structures and tries to invali= date the data cache buffer, which triggers a second attempt to lock an already locked buffer lock and that this might be somehow related to the kernel behaviour described in bug #256936 I will be pointing out this thread to the user that experiences the crashes= , he will be able to add any details about the exact configuration of the affect= ed system. --=20 You are receiving this mail because: You are the assignee for the bug.=