summaryrefslogtreecommitdiffstats
path: root/net/bluetooth/rfcomm/tty.c
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2018-09-14 04:12:15 +0200
committerAl Viro <viro@zeniv.linux.org.uk>2018-10-13 06:50:53 +0200
commitf0193d3ea73b966b5dbfa272c8228d743b8856ef (patch)
treec882a171c8706f274a7e09d8f7297c36ed750e34 /net/bluetooth/rfcomm/tty.c
parentkill TIOCSER[SG]WILD (diff)
downloadlinux-f0193d3ea73b966b5dbfa272c8228d743b8856ef.tar.xz
linux-f0193d3ea73b966b5dbfa272c8228d743b8856ef.zip
change semantics of ldisc ->compat_ioctl()
First of all, make it return int. Returning long when native method had never allowed that is ridiculous and inconvenient. More importantly, change the caller; if ldisc ->compat_ioctl() is NULL or returns -ENOIOCTLCMD, tty_compat_ioctl() will try to feed cmd and compat_ptr(arg) to ldisc's native ->ioctl(). That simplifies ->compat_ioctl() instances quite a bit - they only need to deal with ioctls that are neither generic tty ones (those would get shunted off to tty_ioctl()) nor simple compat pointer ones. Note that something like TCFLSH won't reach ->compat_ioctl(), even if ldisc ->ioctl() does handle it - it will be recognized earlier and passed to tty_ioctl() (and ultimately - ldisc ->ioctl()). For many ldiscs it means that NULL ->compat_ioctl() does the right thing. Those where it won't serve (see e.g. n_r3964.c) are also easily dealt with - we need to handle the numeric-argument ioctls (calling the native instance) and, if such would exist, the ioctls that need layout conversion, etc. All in-tree ldiscs dealt with. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'net/bluetooth/rfcomm/tty.c')
0 files changed, 0 insertions, 0 deletions