From: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>
To: Sreekanth Reddy <sreekanth.reddy@broadcom.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
PDL-MPT-FUSIONLINUX <MPT-FusionLinux.pdl@broadcom.com>,
Sathya Prakash <sathya.prakash@broadcom.com>,
Chaitra Basappa <chaitra.basappa@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
Brian King <brking@linux.vnet.ibm.com>,
mauricfo@linux.vnet.ibm.com, linuxram@us.ibm.com
Subject: Re: [PATCH] mpt3sas: Force request partial completion alignment
Date: Mon, 23 Jan 2017 11:00:48 -0200 [thread overview]
Message-ID: <5885FE80.1030306@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAK=zhgoFH+G-m=VXNAe+ORKUZKJ0e3OY3SvB96_6wS+tB_CQHw@mail.gmail.com>
On 01/23/2017 07:05 AM, Sreekanth Reddy wrote:
> On Wed, Dec 28, 2016 at 6:21 PM, Guilherme G. Piccoli
> <gpiccoli@linux.vnet.ibm.com> wrote:
>> From: Ram Pai <linuxram@us.ibm.com>
>>
>> The firmware or device, possibly under a heavy I/O load, can return
>> on a partial unaligned boundary. Scsi-ml expects these requests to be
>> completed on an alignment boundary. Scsi-ml blindly requeues the I/O
>> without checking the alignment boundary of the I/O request for the
>> remaining bytes. This leads to errors, since devices cannot perform
>> non-aligned read/write operations.
>>
>> This patch fixes the issue in the driver. It aligns unaligned
>> completions of FS requests, by truncating them to the nearest
>> alignment boundary.
>>
>> Reported-by: Mauricio Faria De Oliveira <mauricfo@linux.vnet.ibm.com>
>> Signed-off-by: Guilherme G. Piccoli <gpiccoli@linux.vnet.ibm.com>
>> Signed-off-by: Ram Pai <linuxram@us.ibm.com>
>> ---
>> drivers/scsi/mpt3sas/mpt3sas_scsih.c | 16 ++++++++++++++++
>> 1 file changed, 16 insertions(+)
>>
>> diff --git a/drivers/scsi/mpt3sas/mpt3sas_scsih.c b/drivers/scsi/mpt3sas/mpt3sas_scsih.c
>> index b5c966e..55332a3 100644
>> --- a/drivers/scsi/mpt3sas/mpt3sas_scsih.c
>> +++ b/drivers/scsi/mpt3sas/mpt3sas_scsih.c
>> @@ -4644,6 +4644,8 @@ _scsih_io_done(struct MPT3SAS_ADAPTER *ioc, u16 smid, u8 msix_index, u32 reply)
>> struct MPT3SAS_DEVICE *sas_device_priv_data;
>> u32 response_code = 0;
>> unsigned long flags;
>> + unsigned int sector_sz;
>> + struct request *req;
>>
>> mpi_reply = mpt3sas_base_get_reply_virt_addr(ioc, reply);
>> scmd = _scsih_scsi_lookup_get_clear(ioc, smid);
>> @@ -4703,6 +4705,20 @@ _scsih_io_done(struct MPT3SAS_ADAPTER *ioc, u16 smid, u8 msix_index, u32 reply)
>> }
>>
>> xfer_cnt = le32_to_cpu(mpi_reply->TransferCount);
>> +
>> + /* In case of bogus fw or device, we could end up having
>> + * unaligned partial completion. We can force alignment here,
>> + * then scsi-ml does not need to handle this misbehavior.
>> + */
>> + sector_sz = scmd->device->sector_size;
>> + req = scmd->request;
>> + if (unlikely(sector_sz && req && (req->cmd_type == REQ_TYPE_FS) &&
>> + (xfer_cnt % sector_sz))) {
>> + sdev_printk(KERN_INFO, scmd->device,
>> + "unaligned partial completion avoided\n");
>
> [Sreekanth] Patch looks good. But can we print xfer_cnt & sector_sz
> values along with above print.
>
> Also if it is generic drive issue, then can we move this work around
> to SCSI Mid Layer?
>
Thank you! I'll send a v2 including your suggestion.
Regarding a fix in scsi-ml, we tried already:
https://lkml.org/lkml/2016/12/19/591
Reception wasn't in favor of the patch; they suggested we patch the
driver instead, then we sent the current change only for mpt3sas.
Thanks,
Guilherme
>> + xfer_cnt = (xfer_cnt / sector_sz) * sector_sz;
>> + }
>> +
>> scsi_set_resid(scmd, scsi_bufflen(scmd) - xfer_cnt);
>> if (ioc_status & MPI2_IOCSTATUS_FLAG_LOG_INFO_AVAILABLE)
>> log_info = le32_to_cpu(mpi_reply->IOCLogInfo);
>> --
>> 2.1.0
>>
>
prev parent reply other threads:[~2017-01-23 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 12:51 [PATCH] mpt3sas: Force request partial completion alignment Guilherme G. Piccoli
2017-01-04 11:33 ` Sreekanth Reddy
2017-01-05 16:44 ` Sathya Prakash Veerichetty
2017-01-23 9:05 ` Sreekanth Reddy
2017-01-23 13:00 ` Guilherme G. Piccoli [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=5885FE80.1030306@linux.vnet.ibm.com \
--to=gpiccoli@linux.vnet.ibm.com \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=brking@linux.vnet.ibm.com \
--cc=chaitra.basappa@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=mauricfo@linux.vnet.ibm.com \
--cc=sathya.prakash@broadcom.com \
--cc=sreekanth.reddy@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.com \
/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.