[lwhatley.ctr@navo.hpc.mil: Re: [Pvfs2-developers] Re: [Pvfs2-users] PVFS2 on Infiniband]

Rob Ross rross at mcs.anl.gov
Fri May 19 15:06:57 EDT 2006


what kernel version(s)? -- rob

Pete Wyckoff wrote:
> Lee, I'm forwarding your mail to the developers.  Hopefully somebody
> will notice and guess what's wrong.  I'm having similar issues with
> the 2.4 version on some old vendor-supplied kernel too, but figured
> it was just a local problem.
> 
> 		-- Pete
> 
> 
> ------------------------------------------------------------------------
> 
> Subject:
> Re: [Pvfs2-developers] Re: [Pvfs2-users] PVFS2 on Infiniband
> From:
> "Lee Whatley, Contractor" <lwhatley.ctr at navo.hpc.mil>
> Date:
> Fri, 19 May 2006 12:24:24 -0500
> To:
> Pete Wyckoff <pw at osc.edu>
> 
> To:
> Pete Wyckoff <pw at osc.edu>
> 
> 
> Hi Pete,
> 
> I grabbed the CVS code earlier in the week and finally got around to 
> trying it today.  A "make" runs without a hitch, but "make kmod24" blows 
> up.  Here's what I get:
> 
> [root at scn1 pvfs2-cvs-051906]# make kmod24
>   CC [M] /usr/local/gs/pvfs2-cvs-051906/src/kernel/linux-2.4/devpvfs2-req.o
> devpvfs2-req.c: In function `translate_dev_map':
> devpvfs2-req.c:647: warning: implicit declaration of function 
> `compat_alloc_user_space'
> devpvfs2-req.c:647: warning: initialization makes pointer from integer 
> without a cast
> devpvfs2-req.c:658: warning: implicit declaration of function 
> `copy_in_user'
> devpvfs2-req.c: In function `pvfs2_translate_dev_map':
> devpvfs2-req.c:719: warning: implicit declaration of function 
> `sys_ioctl_Rsmp_208ce54a'
> devpvfs2-req.c: At top level:
> devpvfs2-req.c:722: elements of array `pvfs2_ioctl32_trans' have 
> incomplete type
> devpvfs2-req.c:723: warning: excess elements in struct initializer
> devpvfs2-req.c:723: warning: (near initialization for 
> `pvfs2_ioctl32_trans[0]')
> devpvfs2-req.c:723: warning: excess elements in struct initializer
> devpvfs2-req.c:723: warning: (near initialization for 
> `pvfs2_ioctl32_trans[0]')
> devpvfs2-req.c:724: warning: excess elements in struct initializer
> devpvfs2-req.c:724: warning: (near initialization for 
> `pvfs2_ioctl32_trans[1]')
> devpvfs2-req.c:724: warning: excess elements in struct initializer
> devpvfs2-req.c:724: warning: (near initialization for 
> `pvfs2_ioctl32_trans[1]')
> devpvfs2-req.c:725: warning: excess elements in struct initializer
> devpvfs2-req.c:725: warning: (near initialization for 
> `pvfs2_ioctl32_trans[2]')
> devpvfs2-req.c:725: warning: excess elements in struct initializer
> devpvfs2-req.c:725: warning: (near initialization for 
> `pvfs2_ioctl32_trans[2]')
> devpvfs2-req.c:726: warning: excess elements in struct initializer
> devpvfs2-req.c:726: warning: (near initialization for 
> `pvfs2_ioctl32_trans[3]')
> devpvfs2-req.c:726: warning: excess elements in struct initializer
> devpvfs2-req.c:726: warning: (near initialization for 
> `pvfs2_ioctl32_trans[3]')
> devpvfs2-req.c:727: warning: excess elements in struct initializer
> devpvfs2-req.c:727: warning: (near initialization for 
> `pvfs2_ioctl32_trans[4]')
> devpvfs2-req.c:727: warning: excess elements in struct initializer
> devpvfs2-req.c:727: warning: (near initialization for 
> `pvfs2_ioctl32_trans[4]')
> devpvfs2-req.c:729: warning: excess elements in struct initializer
> devpvfs2-req.c:729: warning: (near initialization for 
> `pvfs2_ioctl32_trans[5]')
> devpvfs2-req.c: In function `pvfs2_ioctl32_init':
> devpvfs2-req.c:737: invalid use of undefined type `struct ioctl_trans'
> devpvfs2-req.c:739: warning: implicit declaration of function 
> `register_ioctl32_conversion_Rsmp_1d2fac6f'
> devpvfs2-req.c:740: invalid use of undefined type `struct ioctl_trans'
> devpvfs2-req.c:740: invalid use of undefined type `struct ioctl_trans'
> devpvfs2-req.c:744: invalid use of undefined type `struct ioctl_trans'
> devpvfs2-req.c:744: invalid use of undefined type `struct ioctl_trans'
> devpvfs2-req.c:749: warning: implicit declaration of function 
> `unregister_ioctl32_conversion_Rsmp_ec2cd46c'
> devpvfs2-req.c:749: invalid use of undefined type `struct ioctl_trans'
> devpvfs2-req.c: In function `pvfs2_ioctl32_cleanup':
> devpvfs2-req.c:758: invalid use of undefined type `struct ioctl_trans'
> devpvfs2-req.c:761: invalid use of undefined type `struct ioctl_trans'
> devpvfs2-req.c:762: invalid use of undefined type `struct ioctl_trans'
> make[1]: *** [devpvfs2-req.o] Error 1
> make: *** [just_kmod24] Error 2
> 
> I'm guessing this has something to do with the fact that I'm using a 
> 64-bit machine, but i dunno for sure.  Any clues?
> 
> Thanks,
> -Lee
> 
> Pete Wyckoff wrote:
>> pw at osc.edu wrote on Tue, 25 Apr 2006 11:10 -0400:
>>
>>> So, in conclusion after all those excuses, I'd love to get back into
>>> some pvfs2-ib debugging with you.  But I'll be sparsely connected
>>> this week (and not working), then completely offline until May 7 or
>>> so.  There has been chatter about a new release soon.  Maybe then
>>> would be a good time for us to get started, hoping that coincides
>>> with my return.  There are other unrelated little messes in the CVS
>>> you may not want to suffer.
>>
>>
>> I've been beating pvfs2 and the IB device in particular, and fixed
>> at least one little bug.  There may be sticklers in the kernel
>> interface that I have not found, though.  If you are excited about
>> doing some testing, please grab CVS head and give it a whirl.
>> Hopefully you can break something that I can reproduce and fix.
>> Thanks for testing.
>>
>>         -- Pete
>>
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Pvfs2-developers mailing list
> Pvfs2-developers at beowulf-underground.org
> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers


More information about the Pvfs2-developers mailing list