[...]
So add "case TUNSETIFF" to the switch statement above.
You discovered the fix for your own bug, so why not implement
it and submit the resulting patch here? :-)
It might have been intentionally left out - but here we go:
--- linux-2.6.10/fs/compat_ioctl.c 2005-02-15 00:09:53.969591354 +0
Take a look at the dev_ifsioc() function in ioctl32.c-- it does not
copy the data back to userspace except for SIOCSIFMAP, and judging
from the strict definition of TUNSETIFF it should not be required to
do so.
IMHO this isn't true -
switch (cmd) {
case SIOCGIFFLAGS:
case SIOCGIFMETRIC:
Hello!
Thanks for the information regarding userland/kernelspace - I think I
understood ...
The reason of my question were problems using the tun/tap interface - I've
got an application (namely l2tpns) demanding the ifreq-structure being
copied back to userspace - which AFAIK doesn't happen in
See arch/sparc64/kernel/ioctl32.c, we translate all of the
structures on the way in and out of userspace when 64-bit
kernel runs 32-bit applications.
Hmm - I don't really get the point - would you mind explaining a little?
Is it the following lines or did I overlook anything:
#define COMPATIBLE_IOC
Hello!
Is there any generic way in situations, where (pointers
to) structs are transferred from user- to kernelspace and vice versa?
Any struct containing a long int or a pointer will have a different
size in kernel space! This usually happens when doing ioctls ...
I'm not sure, whether it caus
vance,
Michael
--
Michael Tautschnig
System operator @ Chair Brauer
Technical University of Munich
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a me
