From: Greg Banks <gnb@melbourne.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: qla2xxxx driver for IA64
Date: Thu, 20 Nov 2003 00:52:33 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106928969122724@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106926349321842@msgid-missing>
David Mosberger wrote:
>
> >>>>> On Wed, 19 Nov 2003 09:10:34 -0800, Evan Felix <evan.felix@pnl.gov> said:
>
> Evan> the IA64 ioctl.h file did not hav the _IOXX_BAD macros, and i
> Evan> added them, i'm not sure how safe that was, but it compiled.
>
> Last time I checked, the _IOXX_BAD macros were not used anywhere in
> the standard kernel and that's why I leaned against including them
> (they seemed like a very temporary thing to me). Perhaps the driver
> could be fixed instead to not use the bad macros?
Andrew,
In the v8.00.00b6 version the function pointer for the ioctl() handler
is not set up in qla2x00_driver_template in qla_os.c so none of the
ioctl()s work anyway.
This patch fixes it.
--- drivers/scsi/qla2xxx.v8.00.00b6.orig/qla_os.c Wed Nov 5 10:48:29 2003
+++ drivers/scsi/qla2xxx/qla_os.c Sat Nov 8 00:54:58 2003
@@ -405,6 +405,7 @@
.module = THIS_MODULE,
.name = DRIVER_NAME,
.proc_name = DRIVER_NAME,
+ .ioctl = qla2x00_ioctl,
.proc_info = qla2x00_proc_info,
.queuecommand = qla2x00_queuecommand,
Also, possibly one of the contributing factors which required
the use of _IOWR_BAD instead of _IOWR is the spurious sizeof()
in exioctln.h:
#define QL_IOCTL_BASE(idx) \
_IOWR_BAD(QLMULTIPATH_MAGIC, idx, sizeof(EXT_IOCTL))
^^^^^^
The macro expects a type as the third argument, not a size (despite
the name of the parameter in the macro definition).
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
next prev parent reply other threads:[~2003-11-20 0:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 17:10 qla2xxxx driver for IA64 Evan Felix
2003-11-19 20:13 ` David Mosberger
2003-11-20 0:52 ` Greg Banks [this message]
2003-11-24 16:54 ` Andrew Vasquez
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=marc-linux-ia64-106928969122724@msgid-missing \
--to=gnb@melbourne.sgi.com \
--cc=linux-ia64@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.