From: Matthew Wilcox <matthew@wil.cx>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: SCSI development list <linux-scsi@vger.kernel.org>,
Klaus Muth <muth@hagos.de>
Subject: Re: [RFC] Sanitize INQUIRY vendor, product and revision strings
Date: Mon, 14 Aug 2006 11:07:31 -0600 [thread overview]
Message-ID: <20060814170730.GE4340@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0608141221520.7399-100000@iolanthe.rowland.org>
On Mon, Aug 14, 2006 at 12:34:56PM -0400, Alan Stern wrote:
> Does anyone object to the patch below? It would help at least one person;
> I'm concerned that it might cause trouble somewhere else.
> @@ -526,6 +519,12 @@ static int scsi_probe_lun(struct scsi_de
> if (response_len > 255)
> response_len = first_inquiry_len; /* sanity */
>
> + /* Sanitize the Vendor, Product, and Revision fields. */
> + for (i = 8; i < 36; ++i) {
> + if (inq_result[i] < 0x20 || inq_result[i] > 0x7e)
> + inq_result[i] = ' ';
> + }
> +
> /*
If we have one non-printable character, should we not overwrite all
subsequent characters with spaces? I'm concerned that they may
NUL-terminate a string, then the remnants be garbage. So in other
words, I'd like to see something like:
void scsi_inquiry_sanitise(unsigned char *inquiry, int start, int end)
{
int i, unprintable = 0;
for (i = start; i < end; i++) {
unprintable |= (inq_result[i] < 0x20 || inq_result[i] > 0x7e)
if (unprintable)
inq_result[i] = ' ';
}
}
and then call it:
scsi_inquiry_sanitise(inq_result, 8, 16);
scsi_inquiry_sanitise(inq_result, 16, 32);
scsi_inquiry_sanitise(inq_result, 32, 36);
This of course begs the questions:
- Do we want to mangle the inquiry return like this?
- Should we simply copy out the strings from the raw inquiry result, and
fix them at copy time
- What about someone who just put a tab in there and now gets
everything overwritten with spaces
That last one could be fixed with a more complex function ...
void scsi_inquiry_sanitise(unsigned char *inquiry, int start, int end)
{
int i, terminated = 0;
for (i = start; i < end; i++) {
terminated |= (inq_result[i] == 0)
if (terminated || inq_result[i] < 0x20 || inq_result[i] > 0x7e)
inq_result[i] = ' ';
}
}
next prev parent reply other threads:[~2006-08-14 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 16:34 [RFC] Sanitize INQUIRY vendor, product and revision strings Alan Stern
2006-08-14 17:07 ` Matthew Wilcox [this message]
2006-08-14 17:37 ` Philip R. Auld
2006-08-14 18:48 ` Stefan Richter
2006-08-14 20:05 ` Alan Stern
2006-08-14 23:52 ` Stefan Richter
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=20060814170730.GE4340@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-scsi@vger.kernel.org \
--cc=muth@hagos.de \
--cc=stern@rowland.harvard.edu \
/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.