two x86_64 fixes for 2.4.21-pre3

two x86_64 fixes for 2.4.21-pre3

Post by Mikael Pettersso » Tue, 04 Feb 2003 21:30:37



Quote:Andi Kleen writes:

 > > 1. One unknown ioctl is logged from RH8.0 init:
 > >
 > > ioctl32(iwconfig:185): Unknown cmd fd(3) cmd(00008b01){00} arg(ffffda90) on socket:[389]
 >
 > Probably harmless, but if you figure it out please send me a patch.

The ioctl is SIOCGIWNAME, which is used by iwconfig from the wireless-tools
package to check if a given net dev is a wireless thing or not (called from
ifup in RedHat as a type test on the net dev).

Unfortunately, include/linux/wireless.h has a big pile of ioctls and arg/res
types that would need to be checked, so I'll defer this to Jean Tourrilhes (cc:d).

/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

two x86_64 fixes for 2.4.21-pre3

Post by Jean Tourrilhe » Tue, 04 Feb 2003 22:30:21



> Andi Kleen writes:
>  > > 1. One unknown ioctl is logged from RH8.0 init:

>  > > ioctl32(iwconfig:185): Unknown cmd fd(3) cmd(00008b01){00} arg(ffffda90) on socket:[389]

>  > Probably harmless, but if you figure it out please send me a patch.

> The ioctl is SIOCGIWNAME, which is used by iwconfig from the wireless-tools
> package to check if a given net dev is a wireless thing or not (called from
> ifup in RedHat as a type test on the net dev).

> Unfortunately, include/linux/wireless.h has a big pile of ioctls and arg/res
> types that would need to be checked, so I'll defer this to Jean Tourrilhes (cc:d).

> /Mikael

        Why don't you just recompile the Wireless Tools (iwconfig and
friends) for 64 bits ?
        The source of Wireless Tools should be 64 bit clean (was
working on Alpha), and I don't think it's worth adding a whole pile of
cruft in the kernel when it's used by a few system utilities that you
can simply recompile. Personally, I expect every distribution to ship
the base system compiled natively.
        With regards to this specific problem, just return an
error. The Wireless Tools should gracefully handle it and report to
the user. I would appreciate if you would use a "distinctive" error
message, such as ENOEXEC, so that I can point users in the correct
direction.

        Just food for thought... I you think the wireless ioctls are
bad, there is worse. The linux-wlan-ng driver defines it's own driver
specific ioctls, and it has 3 times the number of ioctls. Just for one
driver. And the ioctl format sometimes changes with revision.
        So, clearly you can't expect to deal with every ioctl under
the sun, that's just not practical.

        Have fun...

        Jean

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. Nervous with 2.4.21-pre3 and -pre3-ac*

Many people including me are getting unusual Kernel
trouble recently with 2.4.21-pre3-ac*. In my case, with
2.4.21-pre3-ac2 I got segmentation fault from
a command (tar) where I never suspected.   Yet no one seems to know
what part of the the kernel update caused all this
trouble.

Does anyone have any guess?

Regards,

G,. H. S.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Can anyone advise?

3. (revised) fix net/irda warnings for 2.4.21-pre3

4. System hung

5. PATCH: [2.4.21-pre3] Fix for Promise PIO Lockup

6. Help !!!, is there a undelete ?

7. [2.4.21-pre6] update x86_64 for kernel_thread change

8. login script

9. 2.4.21-rc1 on x86_64 oops at shutdown -h

10. Oops in firewire (2.4.21-pre5 with 2.4.21-pre4 firewire driver)

11. 2.4.21-pre3aa1 and RAID0 issue (was: 2.4.21-pre2aa1 - RAID0 issue.)

12. 2.4.21-pre7 & 2.4.21-pre5-ac3 IDE resets

13. Linux 2.4.21-pre3-ac3 and KT400