Date: Sun, 08 Dec 2024 17:10:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 282156] page fault while in kernel mode after 14.0-Release to 14.1-Release upgrade Message-ID: <bug-282156-227-idoJILgrcN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-282156-227@https.bugs.freebsd.org/bugzilla/> References: <bug-282156-227@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=3D282156 --- Comment #9 from Rick Macklem <rmacklem@FreeBSD.org> --- (In reply to Rick Macklem from comment #8) OK, I got the packet traces. It appears that the server is doing a CB_RECALL_ANY (which is not currently supported by the client) and that is causing the crash. It looks like the code should reply NFSERR_NOTSUPP, so I cannot spot an obvious bug. I do not currently have a server that does this callback, but I should be able to hack one to-gether to do testing with. I really should implement the callback. Not sure why 14.0 works and 14.1 does not? If you need to upgrade to 14.1, you could try a couple of workarounds: 1 - Try running the client without the nfscbd daemon (Just delete the nfscbd_enable=3D"YES" line from /etc/rc.conf and reboot it.) or 2 - Use NFSv4.0 by specifying minorversion=3D0 on the mount command line. (It is possible that the default might have been 0 for 14.0. That would explain why the crash occurs on 14.1, but not 14.0.) If you do: # nfsstat -m on the 14.0 client, it will show you what minor version it is using. --=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-282156-227-idoJILgrcN>