Bug 72385 – mkfs.reiser4 segfaults

• Product: Gentoo Linux
• Status: RESOLVED UPSTREAM

[Description Dan Egli 2004-11-24 13:06:11 UTC]

if you try to run mkfs.reiser4 it croaks when trying to create the journal.

Reproducible: Always
Steps to Reproduce:
1. emerge reiser4progrs
2. mkfs.reiser4 /dev/whatever
3. say yes when asked to confirm.

Actual Results:  
Reiser4 is going to be created on /dev/sda1.
(Yes/No): y
Creating reiser4 on /dev/sda1 ... Segmentation fault 

Expected Results:  
create the journal and the FS

Portage 2.0.51-r3 (default-linux/x86/2004.2, gcc-3.3.4, glibc-2.3.4.20041102-r0,
2.6.8-gentoo-r8 i686)
=================================================================
System uname: 2.6.8-gentoo-r8 i686 Pentium III (Coppermine)
Gentoo Base System version 1.6.6
distcc 2.18.2 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.15.92.0.2-r1
Headers:  sys-kernel/linux-headers-2.4.22
Libtools: sys-devel/libtool-1.5.2-r7
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer -pipe "
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown
/usr/kde/3/share/config /usr/lib/fax /usr/lib/mozilla/defaults/pref
/usr/share/config /var/bind /var/qmail/control /var/spool/fax/etc"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer -pipe "
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms"
GENTOO_MIRRORS="http://mirrors.xmission.com/gentoo"
MAKEOPTS="-j4"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alsa apm arts avi berkdb bitmap-fonts cdr crypt cups encode esd f77 fam
foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 imlib jpeg kde libg++
libwww mad mikmod motif mozilla mpeg mysql ncurses nls oggvorbis opengl oss pam
pdflib perl png postgres python qt quicktime readline samba sdl slang spell ssl
svga tcltk tcpd tiff truetype x86 xml2 xmms xv zlib"

[Comment 1 SpanKY 2004-11-29 18:14:30 UTC]

not our problem (we dont support reiser4)

e-mail the upstream dev list and/or file a bug

[Comment 2 Dan Egli 2004-11-29 19:30:03 UTC]

WHO is this upstream people? If I download mkreiser4 from the reiserfs home page and compile it, no problem. So it's not a bug in mkreiser4. It's a bug in one of the patches applied to mkreiser4. If you don't support reiser4, why is the reiser4 tools in portage?

[Comment 3 SpanKY 2004-11-29 19:37:37 UTC]

i assume you mean you downloaded libaal and reiser4progs

i dont know what 'patches' you're refering to, our ebuilds dont apply any

[Comment 4 Dan Egli 2004-11-29 19:55:08 UTC]

if no patches are applied, why can I d/l the same things from namesys, compile using the default options, and have it work flawlessly (except for the kernel not recognising reiser4, which I found out AFTER I filed the bug in the first place)

Here's what the ebuild does:
 * econf: updating /var/tmp/portage/reiser4progs-1.0.2/work/reiser4progs-1.0.2/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating /var/tmp/portage/reiser4progs-1.0.2/work/reiser4progs-1.0.2/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-full-static --disable-mkfs-static --disable-fsck-static --disable-debugfs-static --disable-measurefs-static --disable-cpfs-static --disable-resizefs-static --disable-debug --with-readline --enable-libminimal --sbindir=/sbin --libdir=/lib


My difference when compiling manually was to skip the first 2 steps, and ran configure as:

./configure --prefix=/usr --sysconfdir=/etc

so maybe the bug is somewhere in there?

[Comment 5 SpanKY 2004-11-29 20:04:47 UTC]

the econf: updating messages are 100% harmless (and arent patches :P)

as for the extra configure options, those were applied based upon your USE flags ... again, nothing relating to patching

i'd suggest you try passing diff flags to ./configure and see what's cause the segfault ... either way, no combination of ./configure flags should trigger a segfault -> UPSTREAM problem