From: Tomas Henzl <thenzl@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org,
Andrea Gelmini <andrea.gelmini@gelma.net>,
"Ewan D. Milne" <emilne@redhat.com>
Subject: Re: [PATCH] ses: Fix problems with simple enclosures
Date: Thu, 10 Dec 2015 14:28:29 +0100 [thread overview]
Message-ID: <56697DFD.1000508@redhat.com> (raw)
In-Reply-To: <1449684940.2226.21.camel@HansenPartnership.com>
On 9.12.2015 19:15, James Bottomley wrote:
> On Wed, 2015-12-09 at 18:07 +0100, Tomas Henzl wrote:
>> On 8.12.2015 18:00, James Bottomley wrote:
>>> Simple enclosure implementations (mostly USB) are allowed to return only
>>> page 8 to every diagnostic query. That really confuses our
>>> implementation because we assume the return is the page we asked for and
>>> end up doing incorrect offsets based on bogus information leading to
>>> accesses outside of allocated ranges. Fix that by checking the page
>>> code of the return and giving an error if it isn't the one we asked for.
>>> This should fix reported bugs with USB storage by simply refusing to
>>> attach to enclosures that behave like this. It's also good defensive
>>> practise now that we're starting to see more USB enclosures.
>> Ideally this patch also fixes all callers so they evaluate the return value
>> from ses_recv_diag. That is missed in ses_enclosure_data_process
>> and ses_get_page2_descriptor.
> Well, it wouldn't be a bug fix and it's strictly not necessary. in
> ses_intf_add() we won't attach if the initial retrieve of page 2 fails.
> That means we already have an old copy. So if there's a failure in
> ses_get_page2_descriptor() then we're just working from old data.
> Essentially there's nothing else we could do (except perhaps log the
> problem).
You are right it is very unlikely that we read page2 with success in ses_intf_add
and later page 8 is read instead in ses_get_page2_descriptor and rewrites the page 2.
That means that we no longer have the old copy.
Anyway its almost impossible and your patch per se is correct.
Reviewed-by: Tomas Henzl <thenzl@redhat.com>
Tomas
>
> James
>
>> -tms
>>
>>> Reported-by: Andrea Gelmini <andrea.gelmini@gelma.net>
>>> Cc: stable@vger.kernel.org
>>> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
>>>
>>> ---
>>>
>>> diff --git a/drivers/scsi/ses.c b/drivers/scsi/ses.c
>>> index dcb0d76..7d9cec5 100644
>>> --- a/drivers/scsi/ses.c
>>> +++ b/drivers/scsi/ses.c
>>> @@ -84,6 +84,7 @@ static void init_device_slot_control(unsigned char *dest_desc,
>>> static int ses_recv_diag(struct scsi_device *sdev, int page_code,
>>> void *buf, int bufflen)
>>> {
>>> + int ret;
>>> unsigned char cmd[] = {
>>> RECEIVE_DIAGNOSTIC,
>>> 1, /* Set PCV bit */
>>> @@ -92,9 +93,26 @@ static int ses_recv_diag(struct scsi_device *sdev, int page_code,
>>> bufflen & 0xff,
>>> 0
>>> };
>>> + unsigned char recv_page_code;
>>>
>>> - return scsi_execute_req(sdev, cmd, DMA_FROM_DEVICE, buf, bufflen,
>>> + ret = scsi_execute_req(sdev, cmd, DMA_FROM_DEVICE, buf, bufflen,
>>> NULL, SES_TIMEOUT, SES_RETRIES, NULL);
>>> + if (unlikely(!ret))
>>> + return ret;
>>> +
>>> + recv_page_code = ((unsigned char *)buf)[0];
>>> +
>>> + if (likely(recv_page_code == page_code))
>>> + return ret;
>>> +
>>> + /* successful diagnostic but wrong page code. This happens to some
>>> + * USB devices, just print a message and pretend there was an error */
>>> +
>>> + sdev_printk(KERN_ERR, sdev,
>>> + "Wrong diagnostic page; asked for %d got %u\n",
>>> + page_code, recv_page_code);
>>> +
>>> + return -EINVAL;
>>> }
>>>
>>> static int ses_send_diag(struct scsi_device *sdev, int page_code,
>>>
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-12-10 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 17:00 [PATCH] ses: Fix problems with simple enclosures James Bottomley
2015-12-08 17:06 ` Ewan Milne
2015-12-09 17:07 ` Tomas Henzl
2015-12-09 18:15 ` James Bottomley
2015-12-10 13:28 ` Tomas Henzl [this message]
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=56697DFD.1000508@redhat.com \
--to=thenzl@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andrea.gelmini@gelma.net \
--cc=emilne@redhat.com \
--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