Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 Oct 2025 18:24:19 +0000
From:      bugzilla-noreply@freebsd.org
To:        net@FreeBSD.org
Subject:   [Bug 289734] panic tcp_usr_close while running mount command after configure NFS over TLS
Message-ID:  <bug-289734-7501-H6zpofW4z4@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-289734-7501@https.bugs.freebsd.org/bugzilla/>
References:  <bug-289734-7501@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=3D289734

--- Comment #9 from Gleb Smirnoff <glebius@FreeBSD.org> ---
Most likely this bug belongs to me.  I don't know how restricting number of
threads of rpc.tlsservd helps here, since when we are doing a single mount
there shouldn't be any parallel requests to rpc.tlsservd.  Also, the daemon
still runs with pthreads even when limited to use only one worker thread.

The configuration provided is trivial and apart from some mistakes noticed
by Rick doesn't have anything special.  Of course such trivial configuratio=
ns
were tested with new Netlink RPC transport.  Are you able to reproduce this
crash in a virtual machine or only on hardware?  How many mount/unmount you
need to do to reproduce?  Does the kernel crash data have any sensitive
information or the vmcore can potentially be shared with me?

--=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-289734-7501-H6zpofW4z4>