From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8941] "ls" of an NFSv4 share only works when pumped through strace
Date: Sat, 15 Oct 2016 15:37:59 +0000 [thread overview]
Message-ID: <bug-8941-163-wr5IXqD3XX@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8941-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8941
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks for your bug report, and sorry for the slow response.
Unfortunately, this doesn't really look like a Buildroot problem, but most
likely a kernel problem.
Can you test the same kernel, with another distribution (like a Debian
distribution) ? Which C library are you using ? If you're using uClibc, can you
try glibc ? Is it happening with a different hardware platform, like if you
boot the Buildroot system under Qemu ?
We would really need you to investigate further this bug.
Alternatively, you could provide a detailed step-by-step process on how to
reproduce the bug: a minimal Buildroot Qemu based defconfig that exhibits the
problem, together with the details on how to setup a NFSv4 server. As it is,
it's too much effort to setup everything that's needed to reproduce your bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2016-10-15 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 20:24 [Buildroot] [Bug 8941] New: "ls" of an NFSv4 share only works when pumped through strace bugzilla at busybox.net
2016-10-15 15:37 ` bugzilla at busybox.net [this message]
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=bug-8941-163-wr5IXqD3XX@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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