Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 79103 - (kernel) mdadm segfaults on boot with hardened-sources-2.6.10-r3 when trying to activate a RAID-1 with LVM LVs as source devices
Summary: (kernel) mdadm segfaults on boot with hardened-sources-2.6.10-r3 when trying ...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Hardened (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: The Gentoo Linux Hardened Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-22 08:30 UTC by Milan Holzäpfel
Modified: 2005-03-03 08:40 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Holzäpfel 2005-01-22 08:30:00 UTC
After upgrading to hardened-dev-sources-2.6.10-r3, I get the console output shown at http://mjh.name/files/tmp/DM_on_LVM-Oops.jpg on boot. 

LVM has been activated, and then my softraid-devices should be started; md100 at which the error occurs has two LVM logical volumes as source disks, which are in the same voluma group but on different physical volumes and physical disks. 

This has worked fine with hardened-dev-sources-2.6.10-r1. 

Side note: I have modified my startup- and shutdown scripts, to enable (disable) LVM, then enable (disable) md, and enable (disable) LVM afterwards again, because I have both softraid with LVM LVs as sources and a LVM volume group running on top of a md array.

Reproducible: Always
Steps to Reproduce:
1. Create an md array (here RAID-1) with two LVM logical volumes as source devices.  (I haven't actually tested whether this happens with different setups of this kind too, but I think it should.)
2. Boot with hardened-dev-sources-2.6.10-r3 
Actual Results:  
Oops when the init script runs md to activate the device.

Expected Results:  
Setup the md array normally, just like with hardened-dev-sources-2.6.10-r1

(Note: The compiler usually used is gcc-3.4.3-r1, but for kernels I usually use 
gcc-2.95.3.  GCC is one of the few packages I use from the unstable-branch.  
mdadm has possibly been compiled with an older version of gcc-3.4)

bombax:~ # etcat -v mdadm 
[ Results for search key           : mdadm ]
[ Candidate applications found : 3 ]

 Only printing found installed programs.

*  sys-apps/mdadm :
        [   ] 1.6.0 (0)
        [  I] 1.7.0 (0)
        [M~ ] 1.8.1 (0)
bombax:~ # etcat -v lvm2 
[ Results for search key           : lvm2 ]
[ Candidate applications found : 4 ]

 Only printing found installed programs.

*  sys-fs/lvm2 :
        [  I] 2.00.08 (0)
        [M~ ] 2.00.15 (0)
        [M~ ] 2.00.15-r1 (0)
        [M~ ] 2.00.25 (0)
bombax:~ # 


Portage 2.0.51-r14 (default-linux/x86/2004.3, gcc-2.95.3, glibc-2.3.4.20040808-
r1, 2.6.10-hardened-r1-1 i686)
=================================================================
System uname: 2.6.10-hardened-r1-1 i686 AMD Athlon(tm) 64 Processor 3000+
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4 [2.3.4 (#1, Jan 15 2005, 20:25:51)]
ccache version 2.3 [enabled]
dev-lang/python:     2.3.4
sys-devel/autoconf:  2.59-r5
sys-devel/automake:  1.8.5-r1
sys-devel/binutils:  2.15.92.0.2-r1
sys-devel/libtool:   1.5.2-r7
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-Os -march=k8 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
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/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ 
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/
share/texmf/xdvi/ /var/bind /var/qmail/alias /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-Os -march=k8 -pipe -fomit-frame-pointer"
DISTDIR="/usr/src/pkg"
FEATURES="autoaddcvs autoconfig buildpkg ccache distlocks maketest sandbox 
sfperms strict test userpriv usersandbox"
GENTOO_MIRRORS="ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo http://ftp.uni-
erlangen.de/pub/mirrors/gentoo ftp://gentoo.inode.at/source http://gentoo.inode.
at/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/pkg"
PORTAGE_TMPDIR="/usr/portage/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/portage/local"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="x86 3dnow X aalib acpi acpi4linux alsa apache2 apm arts audiofile avi 
bcmath bdf berkdb bitmap-fonts bzlib cdr crypt cups curl dga dvd encode exif f77 
fam flac font-server foomaticdb fortran freetds freetype fs ftp gd gdbm gif gimp 
gimpprint glut gmp gnome gnutls gphoto2 gpm gstreamer gtk gtk2 iconv imagemagick 
imap imlib innodb ipv6 jabber jack java jpeg junit kde kerberos ldap lesstif 
libg++ libwww mad mailwrapper mcal memlimit mikmod mmap mmx mng motif mpeg mysql 
ncurses nls oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime 
readline sasl scanner sdl slang snmp speex spell sse ssl svga tcltk tcpd tetex 
tiff truetype truetype-fonts type1-fonts unicode usb xine xinerama xml xml2 xmms 
xv xvid zlib linguas_de linguas_en_GB"
Unset:  ASFLAGS, CBUILD, CTARGET, LDFLAGS
Comment 1 Milan Holzäpfel 2005-01-22 08:33:54 UTC
Something which jumped to my head immediately after submitting the bug:  I patched Reiser4 from http://ftp.namesys.com/pub/reiser4-for-2.6/2.6.10/reiser4-for-2.6.10-1.gz into both hardened-dev-sources-2.6.10-r1 and -r3.  This worked for my setup fine with -r1, so assume it hasn't got any effect on it.
Comment 2 Brandon Hale (RETIRED) gentoo-dev 2005-01-22 08:55:06 UTC
We dont support reiser4 in any way, shape, or form. Could you reproduce this without, or is reiser4 your root fs?
Comment 3 Milan Holzäpfel 2005-01-22 11:25:39 UTC
I am actually well aware of that, but I didn't expect you to ask because it worked with -r1.  Yes, I get about the same message with unmodified hardened-sources.  (Despite that I removed the occurences of the "-m32" CFLAG in arch/i386/Makefile and arch/i386/kernel/Makefile, which were added by the -ac patch and break compilitation with gcc-2.95.3.  I think that shouldn't make any difference since gcc-2.95.3 does not create x86_64 executables (does it?) but I can try with gcc-3.3.4 or 3.4.3-r1 if you wish.)
Comment 4 Richard Gray 2005-02-20 11:26:10 UTC
I seem to have a similar problem. 7 SCSI disks in RAID5 seg faults with mdadm -A. I've tried booting with ..28-r5 thro -r7 builds of the O/S and that doesn't seem to help. It's an ext3 file system on the array.
Comment 5 SpanKY gentoo-dev 2005-03-01 15:34:48 UTC
does mdadm-1.9.0 fix things ?  it fixes a segfault that was in 1.8.1 ...
Comment 6 Lars Strojny 2005-03-02 07:23:36 UTC
Use 1.9.0 instead. Works quite fine for me. Maybe 1.9.0 should become stable.
Comment 7 SpanKY gentoo-dev 2005-03-03 08:40:01 UTC
re-open if 1.9.0 doesnt solve the segfault