2005-04-17 06:20:36 +08:00
|
|
|
/* atm.h - general ATM declarations */
|
|
|
|
|
#ifndef _LINUX_ATM_H
|
|
|
|
|
#define _LINUX_ATM_H
|
|
|
|
|
|
2012-10-13 17:46:48 +08:00
|
|
|
#include <uapi/linux/atm.h>
|
2005-04-17 06:20:36 +08:00
|
|
|
|
atm: 32-bit ioctl compatibility
We lack compat ioctl support through most of the ATM code. This patch
deals with most of it, and I can now at least use BR2684 and PPPoATM
with 32-bit userspace.
I haven't added a .compat_ioctl method to struct atm_ioctl, because
AFAICT none of the current users need any conversion -- so we can just
call the ->ioctl() method in every case. I looked at br2684, clip, lec,
mpc, pppoatm and atmtcp.
In svc_compat_ioctl() the only mangling which is needed is to change
COMPAT_ATM_ADDPARTY to ATM_ADDPARTY. Although it's defined as
_IOW('a', ATMIOC_SPECIAL+4,struct atm_iobuf)
it doesn't actually _take_ a struct atm_iobuf as an argument -- it takes
a struct sockaddr_atmsvc, which _is_ the same between 32-bit and 64-bit
code, so doesn't need conversion.
Almost all of vcc_ioctl() would have been identical, so I converted that
into a core do_vcc_ioctl() function with an 'int compat' argument.
I've done the same with atm_dev_ioctl(), where there _are_ a few
differences, but still it's relatively contained and there would
otherwise have been a lot of duplication.
I haven't done any of the actual device-specific ioctls, although I've
added a compat_ioctl method to struct atmdev_ops.
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2008-12-04 14:12:38 +08:00
|
|
|
#ifdef CONFIG_COMPAT
|
|
|
|
|
#include <linux/compat.h>
|
|
|
|
|
struct compat_atmif_sioc {
|
|
|
|
|
int number;
|
|
|
|
|
int length;
|
|
|
|
|
compat_uptr_t arg;
|
|
|
|
|
};
|
|
|
|
|
#endif
|
|
|
|
|
#endif
|