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
| ||
|
Message-ID: <20101205143316.GA9559@fritha.org> Date: Sun, 5 Dec 2010 15:33:16 +0100 From: Heinz Diehl <htd@...tha.org> To: Theodore Tso <tytso@....EDU> Cc: device-mapper development <dm-devel@...hat.com>, Jon Nelson <jnelson@...poni.net>, htejun@...il.com, Matt <jackdachef@...il.com>, Mike Snitzer <snitzer@...hat.com>, Linux Kernel <linux-kernel@...r.kernel.org>, Andi Kleen <andi@...stfloor.org>, Chris Mason <chris.mason@...cle.com>, htd <htd@...cy-poultry.org>, linux-ext4@...r.kernel.org, linux-btrfs <linux-btrfs@...r.kernel.org> Subject: Re: [dm-devel] hunt for 2.6.37 dm-crypt+ext4 corruption? On 05.12.2010, Theodore Tso wrote: > As another thought, what version of GCC are people using who > are having difficulty? Could this perhaps be a compiler-related issue? htd@...sel:~> gcc -v Using built-in specs. Target: x86_64-suse-linux Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.3 --enable-ssp --disable-libssp --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --disable-libgcj --disable-libmudflap --with-slibdir=/lib64 --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --program-suffix=-4.3 --enable-linux-futex --without-system-libunwind --with-cpu=generic --build=x86_64-suse-linux Thread model: posix gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists