From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: libfdisk show stopper on i586?
Date: Wed, 26 Oct 2016 14:37:43 +0200 [thread overview]
Message-ID: <201610261437.44016.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20161026104713.chfwao7rbnxbxkdv@ws.net.home>
On Wednesday 26 October 2016, Karel Zak wrote:
> On Wed, Oct 26, 2016 at 12:27:55PM +0200, Ruediger Meier wrote:
> > On Wednesday 26 October 2016, Karel Zak wrote:
> > > On Wed, Oct 26, 2016 at 11:53:51AM +0200, Ruediger Meier wrote:
> > > > commit 8430b9b88426eb3c273b02a2d9505d839913317c
> > > > Author: Karel Zak <kzak@redhat.com>
> > > > Date: Tue Oct 25 13:41:10 2016 +0200
> > > >
> > > > libfdisk: make script token parser more robust
> > >
> > > Strange, don't see relation between the script parser and fdisk
> > > -l. Do you have LIBFDISK_DEBUG output?
> > >
> > > Karel
> >
> > [ 65s] +14318: libfdisk: INIT: library debug mask: 0xffff
> > [ 65s] +Available "LIBFDISK_DEBUG=<name>[,...]|<mask>" debug
> > masks:
>
> Can you send me the disk image? dd(1) + gzip, it's full of zeros, so
> it should be relatively small.
Hehe, I've made a lot of debugging in a chrooted openSUSE 42.1/i586 and
found out that the problem was
disk-utils/fdisk-menu.c:709:
- unsigned long length;
+ uintmax_t length = 0;
which you have fixed in the meanwhile in e4015b34 ...
But this does not fix the bug in Fedora 19, WTF!?
For the record on openSUSE 42.1/i586 to reproduce the bug these compiler
flags were needed:
CFLAGS='-O2 -D_FORTIFY_SOURCE=2 -fstack-protector'
and this:
$ rm /tmp/gpt.img; truncate -s 1M /tmp/gpt.img
$ echo -e "g\nw\nq\n" | ./fdisk /tmp/gpt.img
$ ./fdisk -l /tmp/gpt.img
<segfault>
Now I'm going to check that on Fedora 19 ...
cu,
Rudi
next prev parent reply other threads:[~2016-10-26 12:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 22:00 libfdisk show stopper on i586? Ruediger Meier
2016-10-26 0:26 ` Yuriy M. Kaminskiy
2016-10-26 8:17 ` Karel Zak
2016-10-26 9:29 ` Ruediger Meier
2016-10-26 9:53 ` Ruediger Meier
2016-10-26 10:19 ` Karel Zak
2016-10-26 10:27 ` Ruediger Meier
2016-10-26 10:47 ` Karel Zak
2016-10-26 12:37 ` Ruediger Meier [this message]
2016-10-26 14:50 ` Ruediger Meier
2016-10-26 10:13 ` Karel Zak
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=201610261437.44016.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=kzak@redhat.com \
--cc=util-linux@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.