From: Stephen Hemminger <stephen@networkplumber.org>
To: linux-nfs@vger.kernel.org
Subject: Fw: [Bug 213135] New: NFS service not working with linux 5.4
Date: Tue, 18 May 2021 14:06:02 -0700 [thread overview]
Message-ID: <20210518140602.018d3908@hermes.local> (raw)
Begin forwarded message:
Date: Tue, 18 May 2021 19:30:28 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 213135] New: NFS service not working with linux 5.4
https://bugzilla.kernel.org/show_bug.cgi?id=213135
Bug ID: 213135
Summary: NFS service not working with linux 5.4
Product: Networking
Version: 2.5
Kernel Version: linux 5.4
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: hbhuwania93@gmail.com
Regression: No
I am running a linux 5.4 kernel image.
I am seeing an issue with NFS service crashing randomly. NFS version I am using
is 2.3.4
Apparently the rpc.mountd crashes randomly and dont have a clear picture on
what is happening. I tried manually launching this daemon and I see below error
traceback:
root@HostName-637562903921812352:/etc# /usr/sbin/rpc.mountd -p 9000 -F -d all
rpc.mountd: Version 2.3.4 starting
rpc.mountd: nfsd_fh: inbuf '* 6 \x8fd3a09e776c46d09e8b8ca1b0e895ec'
rpc.mountd: v4root_create: path '/' flags 0x12407
rpc.mountd: v4root_create: path '/usr' flags 0x10407
rpc.mountd: v4root_create: path '/usr/srvroot' flags 0x10407
*** stack smashing detected ***: <unknown> terminated
Aborted
Any suggestions why NFS is behaving this way?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-05-18 21:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210518140602.018d3908@hermes.local \
--to=stephen@networkplumber.org \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox