From: John Kacur <jkacur@redhat.com>
To: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
wim@iguana.be, Thomas Gleixner <tglx@linutronix.de>,
viro@zeniv.linux.org.uk, Ingo Molnar <mingo@elte.hu>
Cc: Arnd Bergmann <arndbergmann@googlemail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [tip:bkl/drivers] nvram: Drop the BKL from nvram_open()
Date: Wed, 21 Oct 2009 22:09:21 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0910212207240.3526@localhost.localdomain> (raw)
In-Reply-To: <tip-83cb16727085b18191f45eb0ede6bf1f97d67a7a@git.kernel.org>
On Wed, 14 Oct 2009, tip-bot for Ingo Molnar wrote:
> Commit-ID: 83cb16727085b18191f45eb0ede6bf1f97d67a7a
> Gitweb: http://git.kernel.org/tip/83cb16727085b18191f45eb0ede6bf1f97d67a7a
> Author: Ingo Molnar <mingo@elte.hu>
> AuthorDate: Wed, 14 Oct 2009 17:48:38 +0200
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Wed, 14 Oct 2009 17:54:03 +0200
>
> nvram: Drop the BKL from nvram_open()
>
> It's safe to remove the BKL from nvram_open(): there's no open()
> versus read() races: nvram_init() is very simple and race-free,
> it registers the device then puts it into /proc - there's no
> state init to race with.
>
> Cc: Wim Van Sebroeck <wim@iguana.be>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> LKML-Reference: <1255116426-7270-1-git-send-email-fweisbec@gmail.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
> drivers/char/nvram.c | 3 ---
> 1 files changed, 0 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/char/nvram.c b/drivers/char/nvram.c
> index 2100a8f..7cf4518 100644
> --- a/drivers/char/nvram.c
> +++ b/drivers/char/nvram.c
> @@ -329,14 +329,12 @@ static int nvram_ioctl(struct inode *inode, struct file *file,
>
> static int nvram_open(struct inode *inode, struct file *file)
> {
> - lock_kernel();
> spin_lock(&nvram_state_lock);
>
> if ((nvram_open_cnt && (file->f_flags & O_EXCL)) ||
> (nvram_open_mode & NVRAM_EXCL) ||
> ((file->f_mode & FMODE_WRITE) && (nvram_open_mode & NVRAM_WRITE))) {
> spin_unlock(&nvram_state_lock);
> - unlock_kernel();
> return -EBUSY;
> }
>
> @@ -347,7 +345,6 @@ static int nvram_open(struct inode *inode, struct file *file)
> nvram_open_cnt++;
>
> spin_unlock(&nvram_state_lock);
> - unlock_kernel();
>
> return 0;
> }
> --
> To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
This patch and a previous one remove the bkl from the open and llseek
functions. We can also convert to an unlocked_ioctl
>From 8eab1862b12cc851dc2c811261dda7a22d13e83a Mon Sep 17 00:00:00 2001
From: John Kacur <jkacur@redhat.com>
Date: Wed, 21 Oct 2009 21:57:19 +0200
Subject: [PATCH] nvram: Convert nvram_ioctl to unlocked_ioctl
After removing the BKL from open, we can also convert nvram_ioctl to
an unlocked_ioctl. It has it's only spin_lock, and doesn't rely on the BKL
Signed-off-by: John Kacur <jkacur@redhat.com>
---
drivers/char/nvram.c | 17 ++++++++---------
1 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/drivers/char/nvram.c b/drivers/char/nvram.c
index 7cf4518..6c34279 100644
--- a/drivers/char/nvram.c
+++ b/drivers/char/nvram.c
@@ -290,8 +290,7 @@ checksum_err:
return -EIO;
}
-static int nvram_ioctl(struct inode *inode, struct file *file,
- unsigned int cmd, unsigned long arg)
+static long nvram_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
{
int i;
@@ -412,13 +411,13 @@ static int nvram_add_proc_fs(void)
#endif /* CONFIG_PROC_FS */
static const struct file_operations nvram_fops = {
- .owner = THIS_MODULE,
- .llseek = nvram_llseek,
- .read = nvram_read,
- .write = nvram_write,
- .ioctl = nvram_ioctl,
- .open = nvram_open,
- .release = nvram_release,
+ .owner = THIS_MODULE,
+ .llseek = nvram_llseek,
+ .read = nvram_read,
+ .write = nvram_write,
+ .unlocked_ioctl = nvram_ioctl,
+ .open = nvram_open,
+ .release = nvram_release,
};
static struct miscdevice nvram_dev = {
--
1.6.0.6
prev parent reply other threads:[~2009-10-21 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 19:27 [PATCH] nvram: Drop the bkl from non-generic nvram_llseek() Frederic Weisbecker
2009-10-14 15:49 ` [tip:bkl/drivers] " tip-bot for Frederic Weisbecker
2009-10-14 15:58 ` [tip:bkl/drivers] nvram: Drop the BKL from nvram_open() tip-bot for Ingo Molnar
2009-10-21 20:09 ` John Kacur [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.00.0910212207240.3526@localhost.localdomain \
--to=jkacur@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arndbergmann@googlemail.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=wim@iguana.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox