From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: stoyboyker@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, osst@riede.org
Subject: Re: [PATCH 06/13] [scsi] changed ioctls to unlocked
Date: Tue, 24 Mar 2009 21:24:48 +0000 [thread overview]
Message-ID: <1237929888.3308.31.camel@localhost.localdomain> (raw)
In-Reply-To: <1237929168-15341-7-git-send-email-stoyboyker@gmail.com>
On Tue, 2009-03-24 at 16:12 -0500, stoyboyker@gmail.com wrote:
> From: Stoyan Gaydarov <stoyboyker@gmail.com>
>
> Signed-off-by: Stoyan Gaydarov <stoyboyker@gmail.com>
> ---
> drivers/scsi/osst.c | 12 ++++++++----
> 1 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/scsi/osst.c b/drivers/scsi/osst.c
> index 0ea78d9..80e7e98 100644
> --- a/drivers/scsi/osst.c
> +++ b/drivers/scsi/osst.c
> @@ -4856,9 +4856,10 @@ static int os_scsi_tape_close(struct inode * inode, struct file * filp)
>
>
> /* The ioctl command */
> -static int osst_ioctl(struct inode * inode,struct file * file,
> - unsigned int cmd_in, unsigned long arg)
> +static long osst_ioctl(struct file * file, unsigned int cmd_in,
> + unsigned long arg)
> {
> + lock_kernel();
What necessitates the kernel locking? When st was audited, it didn't
need it; since osst is in many ways a copy of st, I'm surprised it does.
James
next prev parent reply other threads:[~2009-03-24 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 21:12 [PATCH 06/13] [scsi] changed ioctls to unlocked stoyboyker
2009-03-24 21:24 ` James Bottomley [this message]
2009-03-24 21:28 ` Stoyan Gaydarov
2009-03-25 4:21 ` Matthew Wilcox
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=1237929888.3308.31.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=osst@riede.org \
--cc=stoyboyker@gmail.com \
/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