From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-progs v3.14 mkfs.btrfs bug: --features long-option segfaults, -O short-option OK
Date: Wed, 16 Apr 2014 06:41:44 +0000 (UTC) [thread overview]
Message-ID: <pan$63522$eac299d1$60270bae$97109238@cox.net> (raw)
Using btrfs-progs v3.14:
mkfs.btrfs ... --features ...
segfaults.
mkfs.btrfs ... -O ...
works fine.
* I used other long options, so it's not simply a problem parsing long
options.
* I tried the long option with various features; none worked, including
--features list-all with no other options. That too segfaulted, tho -O
list-all worked.
Segfault line as logged:
mkfs.btrfs[5231]: segfault at 0 ip 00007fb531c7ab1a sp 00007fffaf1a7a78
error 4 in libc-2.19.so[7fb531bf8000+19a000]
btrfs-progs v3.14 from git on kernel v3.14 from git, gentoo/~amd64, built
with gcc-4.8.2, using glibc-2.19.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next reply other threads:[~2014-04-16 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 6:41 Duncan [this message]
2014-04-16 7:48 ` btrfs-progs v3.14 mkfs.btrfs bug: --features long-option segfaults, -O short-option OK Holger Hoffstätte
2014-04-16 7:55 ` Holger Hoffstätte
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='pan$63522$eac299d1$60270bae$97109238@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).