linux-kernel - modpost segfaults with 32bit compile on 64 bit version of Fedora 13

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 3 Jun 2010 20:00:02 -0700 (PDT)
From:	alan <alan@...eserver.org>
To:	linux-kernel@...r.kernel.org
Subject: modpost segfaults with 32bit compile on 64 bit version of Fedora 13

I have reported this to the Fedora bugzilla. Not getting much traction on 
the problem. Maybe someone here has an idea.

I have a x86_64 version of Fedora 13. I try and build a kernel under i386 
and modpost segfaults every time. (Works fine on Fedora 12 and gcc 4.4.3.)

It does not matter if I use "make ARCH=x86", i386 and make, or any other 
32 bit compile I have tried.

Here is the gcc info:

gcc -v
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man 
--infodir=/usr/share/info 
--with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap 
--enable-shared --enable-threads=posix --enable-checking=release 
--with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions 
--enable-gnu-unique-object 
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada 
--enable-java-awt=gtk --disable-dssi 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre 
--enable-libgcj-multifile --enable-java-maintainer-mode 
--with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib 
--with-ppl --with-cloog --with-tune=generic --with-arch_32=i686 
--build=x86_64-redhat-linux
Thread model: posix
gcc version 4.4.4 20100503 (Red Hat 4.4.4-2) (GCC)

This works under Fedora 12, but not under 13 with the exact same code and 
commands. I have tested with 2.6.35-rc1, as well as other versions.

Any idea what they mangled in gcc 4.4.4 to cause this? So far the Fedora 
people have claimed "it is a kernel problem".

Thanks.

-- 
Truth is stranger than fiction because fiction has to make sense.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/