From: Tastky <tastky@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: [BUG] nfs-utils broken with musl
Date: Tue, 18 Aug 2015 23:58:22 +0200 [thread overview]
Message-ID: <55D3AA7E.2050606@gmail.com> (raw)
As currently being discussed on musl's mailing list, there appears to be
a bug in nfs-utils exposed by musl, which makes rpc.statd loop with:
my_svc_run() - select: Bad file descriptor
URL to list:
http://www.openwall.com/lists/musl/2015/08
The relevant messages begin at August 18 and have 'nfs-utils broken with
musl: "select: Bad file descriptor"' in their titles.
next reply other threads:[~2015-08-18 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 21:58 Tastky [this message]
2015-08-18 23:59 ` [BUG] nfs-utils broken with musl Chuck Lever
2015-08-19 0:33 ` Tastky
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=55D3AA7E.2050606@gmail.com \
--to=tastky@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.