Date: Tue, 29 May 2018 21:19:16 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 228497] [nfs] kernel panic in nfsrv_checksequence Message-ID: <bug-228497-3630-e85K9hOu9s@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-228497-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-228497-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228497 Rick Macklem <rmacklem@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fs@FreeBSD.org |rmacklem@FreeBSD.org Status|New |In Progress CC| |rmacklem@FreeBSD.org --- Comment #1 from Rick Macklem <rmacklem@FreeBSD.org> --- 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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-228497-3630-e85K9hOu9s>