Date: Sat, 04 Dec 2021 01:21:26 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260176] nfsrvd_verify() passes sfp=NULL to nfsv4_loadattr(), which can crash Message-ID: <bug-260176-227-oNPWmz7NeN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260176-227@https.bugs.freebsd.org/bugzilla/> References: <bug-260176-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=3D260176 Rick Macklem <rmacklem@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open Assignee|bugs@FreeBSD.org |rmacklem@FreeBSD.org --- Comment #1 from Rick Macklem <rmacklem@FreeBSD.org> --- Created attachment 229867 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D229867&action= =3Dedit Just reply not same for verify of file system stats attributes To correctly verify file system stats like FILESFREE is somewhat involved and, since no crashes are being reported, not being done by extant NFSv4 clients. Also, I do not see how file system stats that change constantly could be effectively used by VERIFY/NVERIFY. As such, this patch changes the code to just return NFSERR_NOTSAME for them. If a case where the VERIFY needs to work for any of these attributes, a patch for that could be created. This should avoid the crashes. Maybe the reporter can confirm that it fixes the problem for him? --=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-260176-227-oNPWmz7NeN>