Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 05 Sep 2020 13:31:24 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 249127] panic!("docallb") in nfsrv_docallback
Message-ID:  <bug-249127-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D249127

            Bug ID: 249127
           Summary: panic!("docallb") in nfsrv_docallback
           Product: Base System
           Version: 12.1-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: asomers@FreeBSD.org

I just saw this panic on a 12-stable machine.  Unfortunately, I don't have a
core dump, just a stack trace.  It was serving NFS v4.0, with delegations
enabled.  The clients were all Debian, with Linux 3.16.0.

The proximal cause of the panic seems to be that the file had a write
delegation issued to an unconfirmed client.  Root cause is harder to determ=
ine.
 Did the kernel previously issue a delegation to an unconfirmed client?  Or=
 did
the client somehow change to an unconfirmed state after the delegation was
issued, perhaps due to a race?

Should there be a check for LCL_NEEDSCONFIRM somewhere around line 3166 in
nfs_nfsdstate.c?

kdb_backtrace
vpanic
panic
nfsrv_docallback
nfsrv_checkgetattr
nfsrvd_getattr
nfsrvd_dorpc
nfssvc_program
svc_run_internal
svc_thread_start
fork_exit
fork_trampoline

--=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-249127-227>