For the RHEL4 U8 x86_64 system, I'm using the -m elf_x86_64 flag. The 'file' info for this is file ./src/kernel/linux-2.6/pvfs28.ko ./src/kernel/linux-2.6/pvfs28.ko: ELF 64-bit LSB relocatable, AMD x86-64, version 1 (SYSV), not stripped
For the system I'm testing on, the ELF 64-bit is also what shows up for pvfs2-client-core and libpvfs2.so In the panic scenario I have, I don't ever load pvfs2-client/pvfs2-client-core. Simply insmod of pvfs2.ko will cause the kernel panic. In the scenario where I know I will have either both kmod and client-core as 32bit, or both as 64bit, is there something I can do to configure this not to try and do the ioctl32 conversions? -----Original Message----- From: Rob Latham [mailto:[email protected]] Sent: Thursday, March 25, 2010 10:06 AM To: David Metheny Cc: [email protected]; [email protected] Subject: Re: [Pvfs2-developers] PVFS 2.8.2 kernel panics On Thu, Mar 25, 2010 at 08:56:40AM -0500, David Metheny wrote: > Is the register_ioctl32_conversion still needed anymore? I'm not sure when > CONFIG_COMPAT comes into play, or if that is the replacement functionality > for ioctl32 conversions. The one case where you need register_ioctl32 is when you are running a 64 bit kernel, but you built pvfs2-client-core as a 32 bit executable. The PPC64 bi-arch toolchain, for example, defaults to 32 bit. You have to build with "-m64" in your CFLAGS (and LDFLAGS? I forget) to get a 64 bit binary. ==rob -- Rob Latham Mathematics and Computer Science Division Argonne National Lab, IL USA _______________________________________________ Pvfs2-developers mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
