[Bug 297233] nfs: panic: general protection fault

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D297233

--- Comment #10 from Rick Macklem <[email protected]> ---
(In reply to Hans Rosenfeld from comment #8)
> That being said, if you have more information on how exactly you believe =
the
> illumos NFS server to be broken, I'd be happy to help you file an illumos
> bug or file one for you myself. But since my expertise on NFS is quite li=
mited
> I'll need a pretty good explanation of the issue. :-)

It appears that the Illumos server is issuing delegations when
the callback path is not established. This should never happen.
(You can check to be sure by capturing packets for one of these
mounts and looking at the Open replies in wireshark. If any of them
have a delegation, the server is broken.)

Now, having said the above, I don't see much point in your doing so.
NFSv4.0 is deprecated (the Linux folk are discussing disabling it and
may have already done so).

For example, here's what Netapp says on their web site:
BEST PRACTICE: NFSv4.1 or NFSv4.2 should be used instead of NFSv4.0. NFSv4.=
0 is
an older version of the NFS protocol and is no longer actively developed by=
 the
NFS community.
(You can google "NFSv4.0 is deprecated" and get lots more like this.)

> Regarding the FreeBSD panic I'm firmly with Konstantin Belousov here:=20
> FreeBSD should not crash in the NFS client code regardless what any random
> broken NFS server does or does not.
Don't bet on it. It there was an engineering team working on the FreeBSD
NFS client, maybe. But, basically all you've got is one old retired guy
who doesn't get paid any $$$ for doing NFS/FreeBSD work.
(The code the first crash is in was written over 20years ago and this is
the first time I've seen a report of a crash in it. I doubt I'll spot
where the prematuure free() is, but I will take a look one of these days.)
I'll also note that I think "Affects many people" is an exaggeration, given
that I've never seen a crash report from anyone else.

If you really want to track this down, you can comment out "free()" calls
until the crashes go away and then bisect down to the "free()" that
causes the crash, but that is going to be time consuming.

--=20
You are receiving this mail because:
You are the assignee for the bug.=