From owner-freebsd-fs@freebsd.org Tue May 29 21:19:19 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61AC1F76B67 for ; Tue, 29 May 2018 21:19:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D5A707F730 for ; Tue, 29 May 2018 21:19:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8FECCF76B5D; Tue, 29 May 2018 21:19:18 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E570F76B5A for ; Tue, 29 May 2018 21:19:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 178547F72E for ; Tue, 29 May 2018 21:19:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 49A0FDF8F for ; Tue, 29 May 2018 21:19:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4TLJHqE086446 for ; Tue, 29 May 2018 21:19:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4TLJHcK086445 for fs@FreeBSD.org; Tue, 29 May 2018 21:19:17 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: fs@FreeBSD.org Subject: [Bug 228497] [nfs] kernel panic in nfsrv_checksequence Date: Tue, 29 May 2018 21:19:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rmacklem@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: rmacklem@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to bug_status cc attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 May 2018 21:19:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228497 Rick Macklem changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fs@FreeBSD.org |rmacklem@FreeBSD.org Status|New |In Progress CC| |rmacklem@FreeBSD.org --- Comment #1 from Rick Macklem --- Created attachment 193829 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D193829&action= =3Dedit Free up sessions when an ExchangeID with new co_verifier is done This patch might fix the crashes. However, I don't know how the Linux client might have gotten into this situation? (Normally a Linux client only changes the co_verifier when it is hard rebooted via the power cord or similar.) This patch was committed to FreeBSD-current as r333580, but has not been MFC'd. If you could apply this patch to your server(s) and report of you get another crash with the patch applied, that would tell us that something else is broken. Basically a crash like this occurs when the server somehow is using a session when it is free'd. Maybe some sort of network partitioning/client reboot or similar triggered the behaviour that caused the crashes? --=20 You are receiving this mail because: You are the assignee for the bug.=