From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11121] statfs call corrupts memory struct statfs too small
Date: Sat, 30 Jun 2018 19:57:38 +0000 [thread overview]
Message-ID: <bug-11121-163-4QJElHLyIw@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11121-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11121
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #3 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks for reporting the bug to upstream uClibc. I'll close the bug here, since
there isn't much we can do at the Buildroot level about this.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2018-06-30 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 19:15 [Buildroot] [Bug 11121] New: statfs call corrupts memory struct statfs too small bugzilla at busybox.net
2018-06-28 19:33 ` [Buildroot] [Bug 11121] " bugzilla at busybox.net
2018-06-28 23:05 ` bugzilla at busybox.net
2018-06-30 19:57 ` 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-11121-163-4QJElHLyIw@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