From: Noah Misch <noah@cs.caltech.edu>
To: James.Bottomley@SteelEye.com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
axboe@suse.de, schilling@fokus.fhg.de
Subject: [PATCH] Make scsi.h nominally userspace-clean
Date: Mon, 9 Aug 2004 10:24:07 -0700 [thread overview]
Message-ID: <20040809172406.GA1042@orchestra.cs.caltech.edu> (raw)
As Joerg Schilling, the author of cdrecord, has noted in threads such as
http://www.ussg.iu.edu/hypermail/linux/kernel/0309.3/1355.html and
http://www.ussg.iu.edu/hypermail/linux/kernel/0408.0/0799.html,
scsi/scsi.h does not compile cleanly in userspace programs due to its use of
``u8''. I have confirmed this bug and prepared and tested a fix that simply
changes all such uses to ``__u8''. Please consider for inclusion.
I do not argue that including this header file in a program is appropriate, but
other kernel headers already take as many precautions as this patch introduces.
I chose __u8 over uint8_t as more in the style of the kernel generally.
Please keep me on cc:; I do not subscribe to the lists.
Signed-off-by: Noah Misch <noah@cs.caltech.edu>
--- pristine-linux-2.6.8-rc3/include/scsi/scsi.h 2004-06-16 01:20:25.000000000 -0400
+++ zlibstack-linux-2.6.8-rc3/include/scsi/scsi.h 2004-08-09 13:03:27.386545874 -0400
@@ -214,25 +214,25 @@
*/
struct ccs_modesel_head {
- u8 _r1; /* reserved */
- u8 medium; /* device-specific medium type */
- u8 _r2; /* reserved */
- u8 block_desc_length; /* block descriptor length */
- u8 density; /* device-specific density code */
- u8 number_blocks_hi; /* number of blocks in this block desc */
- u8 number_blocks_med;
- u8 number_blocks_lo;
- u8 _r3;
- u8 block_length_hi; /* block length for blocks in this desc */
- u8 block_length_med;
- u8 block_length_lo;
+ __u8 _r1; /* reserved */
+ __u8 medium; /* device-specific medium type */
+ __u8 _r2; /* reserved */
+ __u8 block_desc_length; /* block descriptor length */
+ __u8 density; /* device-specific density code */
+ __u8 number_blocks_hi; /* number of blocks in this block desc */
+ __u8 number_blocks_med;
+ __u8 number_blocks_lo;
+ __u8 _r3;
+ __u8 block_length_hi; /* block length for blocks in this desc */
+ __u8 block_length_med;
+ __u8 block_length_lo;
};
/*
* ScsiLun: 8 byte LUN.
*/
struct scsi_lun {
- u8 scsi_lun[8];
+ __u8 scsi_lun[8];
};
/*
next reply other threads:[~2004-08-09 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 17:24 Noah Misch [this message]
2004-08-09 17:52 ` [PATCH] Make scsi.h nominally userspace-clean Jens Axboe
2004-08-09 20:48 ` V13
2004-08-09 18:26 ` James Courtier-Dutton
-- strict thread matches above, loose matches on Subject: below --
2004-08-09 17:53 Joerg Schilling
2004-08-09 17:53 ` Joerg Schilling
2004-08-09 17:56 ` Jens Axboe
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=20040809172406.GA1042@orchestra.cs.caltech.edu \
--to=noah@cs.caltech.edu \
--cc=James.Bottomley@SteelEye.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=schilling@fokus.fhg.de \
/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.