BKL the next lot
Subsystems (4)
cover BKL the next lot
I started to go through Arnds list of ioctls.
Please review / comment.
Thanks,
tglx
PATCH 1/7 ia64: Remove the BKL from perfmon
pfm_ioctl() is empty and can be safely converted to unlocked_ioctl. We could also remove it, but that would change the return value.
sn_hwperf_ioctl() drops the BKL on entry and reacquires is on exit. Convert to unlocked_ioctl.
--- arch/ia64/kernel/perfmon.c | 21 ++++++++++----------- arch/ia64/sn/kernel/sn2/sn_hwperf.c | 8 ++------ 2 files changed, 12 insertions(+), 17 deletions(-)
arch/ia64/kernel/perfmon.c +10 -11
@@ -1701,8 +1701,7 @@ pfm_poll(struct file *filp, poll_table *return mask; } -static int -pfm_ioctl (struct inode *inode,struct file *file,unsigned int cmd,unsigned long arg) +static long pfm_ioctl (struct file *file,unsigned int cmd,unsigned long arg) {DPRINT (("pfm_ioctl called\n" ));return -EINVAL ;
@@ -2179,15 +2178,15 @@ pfm_no_open(struct inode *irrelevant, ststatic const struct file_operations pfm_file_ops = { - .llseek = no_llseek, - .read = pfm_read, - .write = pfm_write, - .poll = pfm_poll, - .ioctl = pfm_ioctl, - .open = pfm_no_open,/* special open code to disallow open via /proc */ - .fasync = pfm_fasync, - .release = pfm_close, - .flush = pfm_flush + .llseek = no_llseek, + .read = pfm_read, + .write = pfm_write, + .poll = pfm_poll, + .unlocked_ioctl = pfm_ioctl, + .open = pfm_no_open,/* special open code to disallow open via /proc */ + .fasync = pfm_fasync, + .release = pfm_close, + .flush = pfm_flush }; static int
arch/ia64/sn/kernel/sn2/sn_hwperf.c +2 -6
@@ -682,8 +682,7 @@ static int sn_hwperf_map_err(int hwperf_/* * ioctl for "sn_hwperf" misc device */ -static int -sn_hwperf_ioctl (struct inode *in,struct file *fp,u32 op,unsigned long arg) +static long sn_hwperf_ioctl (struct file *fp,u32 op,unsigned long arg) {struct sn_hwperf_ioctl_args a;struct cpuinfo_ia64 *cdata;
@@ -699,8 +698,6 @@ sn_hwperf_ioctl(struct inode *in, structint i;int j; -unlock_kernel (); -/* only user requests are allowed here */ if ((op &SN_HWPERF_OP_MASK ) <10 ) { r = -EINVAL ;
@@ -858,12 +855,11 @@ sn_hwperf_ioctl(struct inode *in, struct error:vfree (p); -lock_kernel ();return r; }static const struct file_operations sn_hwperf_fops = { - .ioctl = sn_hwperf_ioctl, + .unlocked_ioctl = sn_hwperf_ioctl, };static struct miscdevice sn_hwperf_dev = {
PATCH 2/7 m68k: Remove BKL from rtc implementations
In reply to Thomas Gleixnerm68k does not support SMP. The access to the rtc is already serialized with local_irq_save/restore which is sufficient on UP.
The open() protection in arch/m68k/mvme16x/rtc.c is not pretty but sufficient on UP and safe w/o the BKL.
open() in arch/m68k/bvme6000/rtc.c can do with the same atomic logic as arch/m68k/mvme16x/rtc.c
--- arch/m68k/bvme6000/rtc.c | 29 +++++++++-------------------- arch/m68k/mvme16x/rtc.c | 19 +++++-------------- 2 files changed, 14 insertions(+), 34 deletions(-)
arch/m68k/bvme6000/rtc.c +9 -20
@@ -10,7 +10,6 @@#include <linux/errno.h> #include <linux/miscdevice.h> #include <linux/slab.h> -#include <linux/smp_lock.h> #include <linux/ioport.h> #include <linux/capability.h> #include <linux/fcntl.h>
@@ -36,10 +35,9 @@static unsigned char days_in_mo[] = {0 ,31 ,28 ,31 ,30 ,31 ,30 ,31 ,31 ,30 ,31 ,30 ,31 }; -static char rtc_status; +static atomic_t rtc_status =ATOMIC_INIT (1 ); -static int rtc_ioctl (struct inode *inode,struct file *file,unsigned int cmd, -unsigned long arg) +static long rtc_ioctl (struct file *file,unsigned int cmd,unsigned long arg) {volatile RtcPtr_t rtc = (RtcPtr_t )BVME_RTC_BASE ;unsigned char msr;
@@ -133,29 +131,20 @@ static int rtc_ioctl(struct inode *inode }/* -* We enforce only one user at a time here with the open/close. -* Also clear the previous interrupt data on an open, and clean -* up things on a close. +* We enforce only one user at a time here with the open/close. */ -static int rtc_open (struct inode *inode,struct file *file) { -lock_kernel (); -if (rtc_status) { -unlock_kernel (); +if (!atomic_dec_and_test (&rtc_status)) { +atomic_inc (&rtc_status);return -EBUSY ; } - - rtc_status =1 ; -unlock_kernel ();return 0 ; }static int rtc_release (struct inode *inode,struct file *file) { -lock_kernel (); - rtc_status =0 ; -unlock_kernel (); +atomic_inc (&rtc_status);return 0 ; }
@@ -164,9 +153,9 @@ static int rtc_release(struct inode *ino*/ static const struct file_operations rtc_fops = { - .ioctl = rtc_ioctl, - .open = rtc_open, - .release = rtc_release, + .unlocked_ioctl = rtc_ioctl, + .open = rtc_open, + .release = rtc_release, };static struct miscdevice rtc_dev = {
arch/m68k/mvme16x/rtc.c +5 -14
@@ -10,7 +10,6 @@#include <linux/errno.h> #include <linux/miscdevice.h> #include <linux/slab.h> -#include <linux/smp_lock.h> #include <linux/ioport.h> #include <linux/capability.h> #include <linux/fcntl.h>
@@ -37,8 +36,7 @@ static const unsigned char days_in_mo[]static atomic_t rtc_ready =ATOMIC_INIT (1 ); -static int rtc_ioctl (struct inode *inode,struct file *file,unsigned int cmd, -unsigned long arg) +static long rtc_ioctl (struct file *file,unsigned int cmd,unsigned long arg) {volatile MK48T08ptr_t rtc = (MK48T08ptr_t )MVME_RTC_BASE ;unsigned long flags;
@@ -121,22 +119,15 @@ static int rtc_ioctl(struct inode *inode }/* -* We enforce only one user at a time here with the open/close. -* Also clear the previous interrupt data on an open, and clean -* up things on a close. +* We enforce only one user at a time here with the open/close. */ -static int rtc_open (struct inode *inode,struct file *file) { -lock_kernel ();if ( !atomic_dec_and_test (&rtc_ready) ) {atomic_inc ( &rtc_ready ); -unlock_kernel ();return -EBUSY ; } -unlock_kernel (); -return 0 ; }
@@ -151,9 +142,9 @@ static int rtc_release(struct inode *ino*/ static const struct file_operations rtc_fops = { - .ioctl = rtc_ioctl, - .open = rtc_open, - .release = rtc_release, + .unlocked_ioctl = rtc_ioctl, + .open = rtc_open, + .release = rtc_release, }; static struct miscdevice rtc_dev=
Geert Uytterhoeven
maintainerRe: [patch 2/7] m68k: Remove BKL from rtc implementations
Quoted 8 lines · Thomas Gleixner
m68k does not support SMP. The access to the rtc is already serialized with local_irq_save/restore which is sufficient on UP.
The
open()protection inarch/m68k/mvme16x/rtc.cis not pretty but sufficient on UP and safe w/o the BKL.
open()inarch/m68k/bvme6000/rtc.ccan do with the same atomic logic asarch/m68k/mvme16x/rtc.c
Thx, applied.
Quoted 137 lines
Signed-off-by Thomas Gleixner <[email protected]>Cc Geert Uytterhoeven <[email protected]>---
arch/m68k/bvme6000/rtc.c | 29 +++++++++--------------------arch/m68k/mvme16x/rtc.c| 19 +++++--------------2 files changed, 14 insertions(+), 34 deletions(-)Index:
linux-2.6-tip/arch/m68k/bvme6000/rtc.c
===================================================================arch/m68k/bvme6000/rtc.c +0
-1@@ -10,7 +10,6 @@ #include <linux/errno.h> #include <linux/miscdevice.h> #include <linux/slab.h> -#include <linux/smp_lock.h> #include <linux/ioport.h> #include <linux/capability.h> #include <linux/fcntl.h>@@ -36,10 +35,9 @@static unsigned char days_in_mo[] =
{0, 31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31};arch/m68k/bvme6000/rtc.c +2
-3-static char rtc_status; +static atomic_t rtc_status =ATOMIC_INIT (1 ); -static int rtc_ioctl (struct inode *inode,struct file *file,unsigned int cmd, - unsigned long arg) +static long rtc_ioctl (struct file *file,unsigned int cmd,unsigned long arg){
volatileRtcPtr_trtc = (RtcPtr_t)BVME_RTC_BASE; unsigned char msr;arch/m68k/bvme6000/rtc.c +7
-16@@ -133,29 +131,20 @@ static int rtc_ioctl(struct inode *inode } /* - * We enforce only one user at a time here with the open/close. - * Also clear the previous interrupt data on an open, and clean - * up things on a close. + * We enforce only one user at a time here with the open/close. */ - static int rtc_open(struct inode *inode, struct file *file) { - lock_kernel(); - if(rtc_status) { - unlock_kernel(); + if (!atomic_dec_and_test(&rtc_status)) { + atomic_inc(&rtc_status); return -EBUSY; } - - rtc_status = 1; - unlock_kernel(); return 0; } static int rtc_release(struct inode *inode, struct file *file) { - lock_kernel(); - rtc_status = 0; - unlock_kernel(); + atomic_inc(&rtc_status); return 0; }@@ -164,9 +153,9 @@ static int rtc_release(struct inode *ino*/ static const struct file_operations rtc_fops = { - .ioctl = rtc_ioctl, - .open = rtc_open, - .release = rtc_release, + .unlocked_ioctl = rtc_ioctl, + .open = rtc_open, + .release = rtc_release, }; static struct miscdevice rtc_dev = {Index:
linux-2.6-tip/arch/m68k/mvme16x/rtc.c
===================================================================arch/m68k/mvme16x/rtc.c +5
-14@@ -10,7 +10,6 @@ #include <linux/errno.h> #include <linux/miscdevice.h> #include <linux/slab.h> -#include <linux/smp_lock.h> #include <linux/ioport.h> #include <linux/capability.h> #include <linux/fcntl.h>@@ -37,8 +36,7 @@ static const unsigned char days_in_mo[] static atomic_t rtc_ready = ATOMIC_INIT(1); -static int rtc_ioctl (struct inode *inode,struct file *file,unsigned int cmd, - unsigned long arg) +static long rtc_ioctl (struct file *file,unsigned int cmd,unsigned long arg) { volatile MK48T08ptr_t rtc = (MK48T08ptr_t)MVME_RTC_BASE; unsigned long flags;@@ -121,22 +119,15 @@ static int rtc_ioctl(struct inode *inode } /* - * We enforce only one user at a time here with the open/close. - * Also clear the previous interrupt data on an open, and clean - * up things on a close. + * We enforce only one user at a time here with the open/close. */ - static int rtc_open(struct inode *inode, struct file *file) { - lock_kernel(); if( !atomic_dec_and_test(&rtc_ready) ) { atomic_inc( &rtc_ready ); - unlock_kernel(); return -EBUSY; } - unlock_kernel(); - return 0; }@@ -151,9 +142,9 @@ static int rtc_release(struct inode *ino*/ static const struct file_operations rtc_fops = { - .ioctl = rtc_ioctl, - .open = rtc_open, - .release = rtc_release, + .unlocked_ioctl = rtc_ioctl, + .open = rtc_open, + .release = rtc_release, };
Quoted 1 line
static struct miscdevice rtc_dev=
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
PATCH 3/7 powerpc: Use unlocked ioctl in nvram_64
In reply to Thomas GleixnerThe ioctl is only used for powermac systems and reads a partition number from an array which is initialized at boot time way before the nvram code is initialized. So it's safe to switch to unlocked_ioctl.
--- arch/powerpc/kernel/nvram_64.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
arch/powerpc/kernel/nvram_64.c +7 -7
@@ -139,8 +139,8 @@ out: } -static int dev_nvram_ioctl (struct inode *inode,struct file *file, -unsigned int cmd,unsigned long arg) +static long dev_nvram_ioctl (struct file *file,unsigned int cmd, +unsigned long arg) {switch (cmd) {#ifdef CONFIG_PPC_PMAC
@@ -169,11 +169,11 @@ static int dev_nvram_ioctl(struct inode }const struct file_operations nvram_fops = { - .owner =THIS_MODULE , - .llseek = dev_nvram_llseek, - .read = dev_nvram_read, - .write = dev_nvram_write, - .ioctl = dev_nvram_ioctl, + .owner =THIS_MODULE , + .llseek = dev_nvram_llseek, + .read = dev_nvram_read, + .write = dev_nvram_write, + .unlocked_ioctl = dev_nvram_ioctl, };static struct miscdevice nvram_dev = {
PATCH 4/7 sh: Remove BKL from landisk gio
In reply to Thomas GleixnerThe open function got the BKL via the big push down. Replace it by preempt_enable/disable as this is sufficient for an UP machine.
The ioctl can be unlocked because there is no functionality which requires serialization. The usage by multiple callers is broken with and without the BKL due to the local static variable addr.
--- arch/sh/boards/mach-landisk/gio.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-)
arch/sh/boards/mach-landisk/gio.c +4 -6
@@ -14,7 +14,6 @@*/ #include <linux/module.h> #include <linux/init.h> -#include <linux/smp_lock.h> #include <linux/kdev_t.h> #include <linux/cdev.h> #include <linux/fs.h>
@@ -35,7 +34,7 @@ static int gio_open(struct inode *inode,int minor;int ret = -ENOENT ; -lock_kernel (); +preempt_disable (); minor =MINOR (inode->i_rdev);if (minor <DEVCOUNT ) {if (openCnt >0 ) {
@@ -45,7 +44,7 @@ static int gio_open(struct inode *inode, ret =0 ; } } -unlock_kernel (); +preempt_enable ();return ret; }
@@ -60,8 +59,7 @@ static int gio_close(struct inode *inodereturn 0 ; } -static int gio_ioctl (struct inode *inode,struct file *filp, -unsigned int cmd,unsigned long arg) +static long gio_ioctl (struct file *filp,unsigned int cmd,unsigned long arg) {unsigned int data;static unsigned int addr =0 ;
@@ -129,7 +127,7 @@ static const struct file_operations gio_ .owner = THIS_MODULE, .open = gio_open, /* open */ .release = gio_close, /* release */ - .ioctl = gio_ioctl, /* ioctl */ + .unlocked_ioctl = gio_ioctl, };static int __init gio_init (void )
Paul Mundt
AppliedRe: [patch 4/7] sh: Remove BKL from landisk gio
Quoted 9 lines · Thomas Gleixner
The open function got the BKL via the big push down. Replace it by preempt_enable/disable as this is sufficient for an UP machine.
The ioctl can be unlocked because there is no functionality which requires serialization. The usage by multiple callers is broken with and without the BKL due to the local static variable addr.
Signed-off-by Thomas Gleixner <[email protected]>Cc Paul Mundt <[email protected]>
Applied to my 2.6.32 queue, thanks Thomas.
PATCH 5/7 um: Convert hostaudio to unlocked ioctl
In reply to Thomas GleixnerThe hostaudio ioctls can be converted to unlocked ioctls for the following reasons:
- get/put_user do not require the BKL
- os_ioctl_generic() passes the ioctl to the host and does not need serialization.
--- arch/um/drivers/hostaudio_kern.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
arch/um/drivers/hostaudio_kern.c +6 -6
@@ -136,8 +136,8 @@ static unsigned int hostaudio_poll(strucreturn mask; } -static int hostaudio_ioctl (struct inode *inode,struct file *file, -unsigned int cmd,unsigned long arg) +static long hostaudio_ioctl (struct file *file,unsigned int cmd, +unsigned long arg) {struct hostaudio_state *state = file->private_data;unsigned long data =0 ;
@@ -223,8 +223,8 @@ static int hostaudio_release(struct inod/* /dev/mixer file operations */ -static int hostmixer_ioctl_mixdev (struct inode *inode,struct file *file, -unsigned int cmd,unsigned long arg) +static long hostmixer_ioctl_mixdev (struct file *file,unsigned int cmd, +unsigned long arg) {struct hostmixer_state *state = file->private_data;
@@ -289,7 +289,7 @@ static const struct file_operations host .read = hostaudio_read, .write = hostaudio_write, .poll = hostaudio_poll, - .ioctl = hostaudio_ioctl, + .unlocked_ioctl = hostaudio_ioctl, .mmap = NULL, .open = hostaudio_open, .release = hostaudio_release,
@@ -298,7 +298,7 @@ static const struct file_operations hoststatic const struct file_operations hostmixer_fops = { .owner =THIS_MODULE , .llseek = no_llseek, - .ioctl = hostmixer_ioctl_mixdev, + .unlocked_ioctl = hostmixer_ioctl_mixdev, .open = hostmixer_open_mixdev, .release = hostmixer_release, };
PATCH 6/7 um: Convert mmapper to unlocked_ioctl
In reply to Thomas GleixnerThe ioctl is empty and needs no serialization. We might remove it completely but that would change the return value from -ENOIOCTLCMD to -ENOTTY.
--- arch/um/drivers/mmapper_kern.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
arch/um/drivers/mmapper_kern.c +3 -3
@@ -46,8 +46,8 @@ static ssize_t mmapper_write(struct filereturn count; } -static int mmapper_ioctl (struct inode *inode,struct file *file, -unsigned int cmd,unsigned long arg) +static long mmapper_ioctl (struct file *file,unsigned int cmd, +unsigned long arg) {return -ENOIOCTLCMD ; }
@@ -91,7 +91,7 @@ static const struct file_operations mmap .owner = THIS_MODULE, .read = mmapper_read, .write = mmapper_write, - .ioctl = mmapper_ioctl, + .unlocked_ioctl = mmapper_ioctl, .mmap = mmapper_mmap, .open = mmapper_open, .release = mmapper_release,
Re: [patch 6/7] um: Convert mmapper to unlocked_ioctl
Quoted 6 lines · Thomas Gleixner
The ioctl is empty and needs no serialization. We might remove it completely but that would change the return value from
-ENOIOCTLCMDto-ENOTTY.Signed-off-by Thomas Gleixner <[email protected]>Cc Jeff Dike <[email protected]>
This one is tricky if you want to get it right according to the book. ENOIOCTLCMD is never a valid return code for user space, but sys_ioctl passes it down anyway.
However, returning -ENOIOCTLCMD from an *unlocked_ioctl* function automatically gets turned into -EINVAL. It does this to allow the same functions to be used for unlocked_ioctl and compat_ioctl. In effect, this patch is functionally identical to removing the ioctl function, which I think is what should be done here.
Arnd <><
Re: [patch 6/7] um: Convert mmapper to unlocked_ioctl
Quoted 12 lines · Arnd Bergmann
Quoted 6 lines · Thomas Gleixner
The ioctl is empty and needs no serialization. We might remove it completely but that would change the return value from
-ENOIOCTLCMDto-ENOTTY.Signed-off-by Thomas Gleixner <[email protected]>Cc Jeff Dike <[email protected]>This one is tricky if you want to get it right according to the book. ENOIOCTLCMD is never a valid return code for user space, but
sys_ioctlpasses it down anyway.
Quoted 5 lines
However, returning
-ENOIOCTLCMDfrom an *unlocked_ioctl* function automatically gets turned into-EINVAL. It does this to allow the same functions to be used forunlocked_ioctlandcompat_ioctl. In effect, this patch is functionally identical to removing the ioctl function, which I think is what should be done here.
Yeah, we get either -ENOTTY or -EINVAL which always changes the user space return value. So yes, removing it at least saves some line of code :)
Thanks,
tglx
Re: [patch 6/7] um: Convert mmapper to unlocked_ioctl
In reply to Arnd BergmannQuoted 12 lines · On Thu, 15 Oct 2009 15:00:34 +0200 Arnd Bergmann <[email protected]>…
Quoted 6 lines · Thomas Gleixner
The ioctl is empty and needs no serialization. We might remove it completely but that would change the return value from
-ENOIOCTLCMDto-ENOTTY.Signed-off-by Thomas Gleixner <[email protected]>Cc Jeff Dike <[email protected]>This one is tricky if you want to get it right according to the book. ENOIOCTLCMD is never a valid return code for user space, but
sys_ioctlpasses it down anyway.
Quoted 5 lines
However, returning
-ENOIOCTLCMDfrom an *unlocked_ioctl* function automatically gets turned into-EINVAL. It does this to allow the same functions to be used forunlocked_ioctlandcompat_ioctl. In effect, this patch is functionally identical to removing the ioctl function, which I think is what should be done here.
That is wrong.
SuS requires an unknown ioctl code returns -ENOTTY. If the code is currently remapping it to EINVAL then it wants fixing.
Re: [patch 6/7] um: Convert mmapper to unlocked_ioctl
Quoted 9 lines · Alan Cox
Quoted 5 lines · On Thu, 15 Oct 2009 15:00:34 +0200 Arnd Bergmann <[email protected]>…
However, returning
-ENOIOCTLCMDfrom an *unlocked_ioctl* function automatically gets turned into-EINVAL. It does this to allow the same functions to be used forunlocked_ioctlandcompat_ioctl. In effect, this patch is functionally identical to removing the ioctl function, which I think is what should be done here.
Quoted 4 lines
That is wrong.
SuS requires an unknown ioctl code returns
-ENOTTY. If the code is currently remapping it to EINVAL then it wants fixing.
Right, I forgot about the EINVAL/ENOTTY difference. The code currently returns -ENOIOCTLCMD, which is worse. Thomas' patch makes it return -EINVAL, which as you said is still wrong. Removing the ioctl function will do the right thing and return -ENOTTY, so that should be done here in um/mmapper, with an appropriate changelog.
For the common code in fs/ioctl.c, I think the current behaviour is correct. It returns -EINVAL if the driver returns -ENOIOCTLCMD, iow "the request [...] argument is not valid for this device", as specified by http://www.opengroup.org/onlinepubs/009695399/functions/ioctl.html.
Drivers returning ENOIOCTLCMD for every request are broken and should be changed to have no ioctl function.
Arnd <><
Re: [patch 6/7] um: Convert mmapper to unlocked_ioctl
Quoted 15 lines · Arnd Bergmann
Quoted 9 lines · Alan Cox
Quoted 5 lines · On Thu, 15 Oct 2009 15:00:34 +0200 Arnd Bergmann <[email protected]>…
However, returning
-ENOIOCTLCMDfrom an *unlocked_ioctl* function automatically gets turned into-EINVAL. It does this to allow the same functions to be used forunlocked_ioctlandcompat_ioctl. In effect, this patch is functionally identical to removing the ioctl function, which I think is what should be done here.Quoted 4 lines
That is wrong.
SuS requires an unknown ioctl code returns
-ENOTTY. If the code is currently remapping it to EINVAL then it wants fixing.
Quoted 8 lines
Right, I forgot about the EINVAL/ENOTTY difference. The code currently returns
-ENOIOCTLCMD, which is worse. Thomas' patch makes it return-EINVAL, which as you said is still wrong. Removing the ioctl function will do the right thing and return-ENOTTY, so that should be done here in um/mmapper, with an appropriate changelog.For the common code in
fs/ioctl.c, I think the current behaviour is correct. It returns-EINVALif the driver returns-ENOIOCTLCMD, iow
Only the unlocked_ioctl code path, the locked one returns whatever crap comes from the ioctl implementation.
Quoted 5 lines
"the request [...] argument is not valid for this device", as specified by http://www.opengroup.org/onlinepubs/009695399/functions/ioctl.html.
Drivers returning ENOIOCTLCMD for every request are broken and should be changed to have no ioctl function.
Ack.
tglx
PATCH 7/7 um: Remove BKL from harddog
In reply to Thomas GleixnerIt's safe to remove the BKL from harddog because:
- open() needs no serialization versus init
- open() is already serialized with a local lock
- ioctl() does not need BKL for put/copy_user
- ioctl() does not need BKL for pin_watchdog as it simply writes to the fd which was created in open()
--- arch/um/drivers/harddog_kern.c | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-)
arch/um/drivers/harddog_kern.c +3 -7
@@ -42,7 +42,6 @@#include <linux/miscdevice.h> #include <linux/watchdog.h> #include <linux/reboot.h> -#include <linux/smp_lock.h> #include <linux/init.h> #include <linux/spinlock.h> #include <asm/uaccess.h>
@@ -66,7 +65,6 @@ static int harddog_open(struct inode *inint err = -EBUSY ;char *sock =NULL ; -lock_kernel ();spin_lock (&lock);if (timer_alive) goto err;
@@ -83,11 +81,9 @@ static int harddog_open(struct inode *in timer_alive =1 ;spin_unlock (&lock); -unlock_kernel ();return nonseekable_open (inode, file); err:spin_unlock (&lock); -unlock_kernel ();return err; }
@@ -124,8 +120,8 @@ static ssize_t harddog_write(struct filereturn 0 ; } -static int harddog_ioctl (struct inode *inode,struct file *file, -unsigned int cmd,unsigned long arg) +static long harddog_ioctl (struct file *file,unsigned int cmd, +unsigned long arg) {void __user *argp= (void __user *)arg;static struct watchdog_info ident = {
@@ -151,7 +147,7 @@ static int harddog_ioctl(struct inode *istatic const struct file_operations harddog_fops = { .owner =THIS_MODULE , .write = harddog_write, - .ioctl = harddog_ioctl, + .unlocked_ioctl = harddog_ioctl, .open = harddog_open, .release = harddog_release, };