From: krike@sci.fi
To: James.Bottomley@suse.de
Cc: linux-scsi@vger.kernel.org
Subject: include/scsi/scsi.h: type mismatch in userspace
Date: Tue, 26 Jan 2010 12:09:06 +0200 [thread overview]
Message-ID: <20100126100905.GA3600@sci.fi> (raw)
In-Reply-To: <20100121170158.GB13617@suse.de>
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
Hello.
I think that there is mistake in linux/2.6.32.4/include/scsi/scsi.h:
the type defination of u8 should be type of __u8 on userspace
(struct scsi_varlen_cdb_hdr).
I founded this problem when I try compile the util-linux-ng-2.17.
This should cause problems many other packages also that includes scsi.h
>
> Please let the Linux SCSI developers know about this, they are the ones
> responsible for fixing it. Once they have done so in the upstream tree,
> can I add it to the -stable tree.
>
> thanks,
>
> greg k-h
Best regards: Kristian Rainio <krike@sci.fi>
[-- Attachment #2: linux-2.6.32.5-scsi_h.patch --]
[-- Type: text/plain, Size: 679 bytes --]
Patch by Kristian Rainio
Little fix.
--- linux-2.6.32/include/scsi/scsi.h.orig 2010-01-23 12:39:06.970791908 +0200
+++ linux-2.6.32/include/scsi/scsi.h 2010-01-23 12:39:25.427462244 +0200
@@ -145,10 +145,10 @@
/* defined in T10 SCSI Primary Commands-2 (SPC2) */
struct scsi_varlen_cdb_hdr {
- u8 opcode; /* opcode always == VARIABLE_LENGTH_CMD */
- u8 control;
- u8 misc[5];
- u8 additional_cdb_length; /* total cdb length - 8 */
+ __u8 opcode; /* opcode always == VARIABLE_LENGTH_CMD */
+ __u8 control;
+ __u8 misc[5];
+ __u8 additional_cdb_length; /* total cdb length - 8 */
__be16 service_action;
/* service specific data follows */
};
next parent reply other threads:[~2010-01-26 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100121090042.GA2083@satellite>
[not found] ` <20100121170158.GB13617@suse.de>
2010-01-26 10:09 ` krike [this message]
2010-02-18 6:44 ` include/scsi/scsi.h: type mismatch in userspace krike
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=20100126100905.GA3600@sci.fi \
--to=krike@sci.fi \
--cc=James.Bottomley@suse.de \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).