From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6428] New: util-linux libmount segfaults with patch from buildroot
Date: Sun, 11 Aug 2013 20:37:59 +0000 (UTC) [thread overview]
Message-ID: <bug-6428-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6428
Summary: util-linux libmount segfaults with patch from
buildroot
Product: buildroot
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: daniel at exxm.de
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 5012
--> https://bugs.busybox.net/attachment.cgi?id=5012
Patch
The patch file package/util-linux/util-linux-001-sscanf-no-ms-as.patch
introduces a bug in libmount that causes /bin/mount to segfault most of the
time. As a result, the root filesystem does not get remounted read/write.
The reason it segfaults is that it passes a (char **) where sscanf expects a
(char *).
You could also use a different patch from
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-apps/util-linux/files/util-linux-2.21.1-no-printf-alloc.patch?revision=1.2
If you do so, be careful! It's against 2.21.1. 2.22 introduced the function
mnt_parse_swaps_line() which also makes use of the %a modifier. You'd need to
enhance the patch to fix mnt_parse_swaps_line() as well.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2013-08-11 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 20:37 bugzilla at busybox.net [this message]
2013-10-31 10:23 ` [Buildroot] [Bug 6428] util-linux libmount segfaults with patch from buildroot bugzilla at busybox.net
2013-11-22 6:47 ` bugzilla at busybox.net
2013-11-28 13:56 ` bugzilla at busybox.net
2013-11-28 16:52 ` bugzilla at busybox.net
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-6428-163@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