From: xtraeme <xtraeme@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] rpc.mountd musl segmentation fault
Date: Mon, 17 Feb 2020 06:02:25 +0100 [thread overview]
Message-ID: <20200217050225.HP0WRTpdeJ8T0U0GEiVvbq6V2NxP_hpHGU9QMhdrpm8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-8569@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]
Closed issue by herveq1 on void-packages repository
https://github.com/void-linux/void-packages/issues/8569
Description:
### System
* xuname:
Void 4.19.20_1 x86_64-musl GenuineIntel notuptodate hold rrFFFFFF
*output of ``xuname`` (part of xtools)*
* package:
*affected package(s) including the version*
xq nfs-utils
[*] nfs-utils-1.3.4_6 Network File System utilities
### Expected behavior
do what is is intended to do...
### Actual behavior
rpc.mountd musl version segmentation fault on server when mounting the directory on client.
Works ok on Void glibc machine!
/var/log/messages
2019-02-12T09:02:33.754663+01:00 olix rpc.mountd[3106]: Version 1.3.3 starting
2019-02-12T09:02:33.809015+01:00 olix kernel: [ 4534.671414] rpc.mountd[3106]: segfault at 28 ip 00007fc73d9e0534 sp 00007ffeea9f2bf0 error 4 in libc.so[7fc73d9b2000+62000]
2019-02-12T09:02:33.809046+01:00 olix kernel: [ 4534.671423] Code: 84 00 00 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 41 54 55 53 <48> 8b 47 28 48 85 c0 74 63 b9 01 00 00 00 eb 07 0f 1f 40 00 48 89
2019-02-12T09:02:33.835026+01:00 olix kernel: [ 4534.697132] nfsd: last server has exited, flushing export cache
### Steps to reproduce the behavior
start nfs on server
try to mount an exported directory on the client
parent reply other threads:[~2020-02-17 5:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-8569@inbox.vuxu.org>]
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=20200217050225.HP0WRTpdeJ8T0U0GEiVvbq6V2NxP_hpHGU9QMhdrpm8@z \
--to=xtraeme@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).