I believe, if my memory is working right, that is the same
problem we saw on s390x which caused us to change the
#define __SID ...
in LiS/include/sys/gnu.stropts.h and LiS/include/sys/stropts.h
If you look at the patch(es) I sent, they redefine __SID to have
a higher starting/base value to avoid a collision with some
linux kernel defined ioctl. If you change __SID your LiS dependent
drivers have to be recompiled with that same __SID.
If you took the __SID part out of the patch, try putting it
back in. I don't have easy access to a RHEL4-x86_64 system
right now, but I should be able to check this out more early
next week if that suggestion does not help.
[EMAIL PROTECTED]
02/10/2006 05:18 PM |
|
>
> When I do insmod I see the following messages:
> redhat64 kernel: Trying to register duplicated ioctl32 handler 5309
> redhat64 kernel: Trying to register duplicated ioctl32 handler 5306
> redhat64 kernel: Trying to register duplicated ioctl32 handler 5302
> redhat64 kernel: Trying to register duplicated ioctl32 handler 530c
> redhat64 kernel: Trying to register duplicated ioctl32 handler 530d
> redhat64 kernel: Trying to register duplicated ioctl32 handler 5308
>
> Which apparently caused by :
> lis_init_module()
> {
> ...
> #if (defined(_S390X_LIS_) || defined(_PPC64_LIS_) || defined(_X86_64_LIS_))
> register_ioctl32_conversion(I_SETSIG,sys_ioctl);
> register_ioctl32_conversion(I_SRDOPT,sys_ioctl);
> register_ioctl32_conversion(I_PUSH,sys_ioctl);
> r>egister_ioctl32_conversion(I_LINK,sys_ioctl);
> register_ioctl32_conversion(I_UNLINK,sys_ioctl);
> register_ioctl32_conversion(I_STR,lis_ioctl32_str);
> #endif
> What is the significance of that ?
> Am I in danger?
> Eugene

