summaryrefslogtreecommitdiffstats
path: root/arch/um
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2019-06-03 14:23:09 +0200
committerArnd Bergmann <arnd@arndb.de>2019-10-23 17:23:46 +0200
commitb6dfb2477fb0bf48e31999d306d2552144891f6e (patch)
tree885f697cc31b700310c1b9aed6b3d4100f474387 /arch/um
parent314999dcbca75c3ca8aaba102875d51ab409cf87 (diff)
downloadlinux-b6dfb2477fb0bf48e31999d306d2552144891f6e.tar.gz
linux-b6dfb2477fb0bf48e31999d306d2552144891f6e.tar.bz2
linux-b6dfb2477fb0bf48e31999d306d2552144891f6e.zip
compat_ioctl: move WDIOC handling into wdt drivers
All watchdog drivers implement the same set of ioctl commands, and fortunately all of them are compatible between 32-bit and 64-bit architectures. Modern drivers always go through drivers/watchdog/wdt.c as an abstraction layer, but older ones implement their own file_operations on a character device for this. Move the handling from fs/compat_ioctl.c into the individual drivers. Note that most of the legacy drivers will never be used on 64-bit hardware, because they are for an old 32-bit SoC implementation, but doing them all at once is safer than trying to guess which ones do or do not need the compat_ioctl handling. Reviewed-by: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'arch/um')
-rw-r--r--arch/um/drivers/harddog_kern.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/um/drivers/harddog_kern.c b/arch/um/drivers/harddog_kern.c
index 000cb69ba0bc..e6d4f43deba8 100644
--- a/arch/um/drivers/harddog_kern.c
+++ b/arch/um/drivers/harddog_kern.c
@@ -165,6 +165,7 @@ static const struct file_operations harddog_fops = {
.owner = THIS_MODULE,
.write = harddog_write,
.unlocked_ioctl = harddog_ioctl,
+ .compat_ioctl = compat_ptr_ioctl,
.open = harddog_open,
.release = harddog_release,
.llseek = no_llseek,