From: Namjae Jeon <linkinjeon@gmail.com>
To: Santosh Y <santoshsy@gmail.com>
Cc: james.bottomley@hansenpartnership.com,
linux-scsi@vger.kernel.org, yoshitake.kobayashi@toshiba.co.jp,
vinholikatti@gmail.com
Subject: Re: [PATCH 1/2] [SCSI] ufs: update Response UPIU length in dword
Date: Sun, 8 Apr 2012 16:00:16 +0900 [thread overview]
Message-ID: <CAKYAXd-_VQRCVeB6TsvL17=ZfCnafcmj++HBi-xfT7k4cGGC-w@mail.gmail.com> (raw)
In-Reply-To: <1333715241-32346-1-git-send-email-santoshsy@gmail.com>
2012/4/6 Santosh Y <santoshsy@gmail.com>:
> UFSHCI spec mentions that Response UPIU Length(RUL)
> field in Transfer Request Descriptor should be in dword.
>
> Query Response UPIU size is variable depending on the data
> to be read/written and the size of a SCSI command Response
> UPIU is fixed.
>
> Currently response_upiu_length is being updated in bytes.
> If a UFS host controller prepares a Query Response UPIU
> with response_upiu_length, it will result in wrong Query
> Response UPIU size corrupting the command descriptor list.
>
> This issue will not affect the current UFSHCD Ver 0.1,
> since Query function support is not yet implemented.
> But this patch also ensures against command descriptor list
> corruption if a UFS controller prepares SCSI Response UPIU
> with response_upiu_length.
>
> Reported-by: KOBAYASHI Yoshitake <yoshitake.kobayashi@toshiba.co.jp>
> Reviewed-by: Vinayak Holikatti <vinholikatti@gmail.com>
> Signed-off-by: Santosh Y <santoshsy@gmail.com>
Hi Santosh.
I also checked it on UFS specification. Looks good to me.
Reviewed-by: Namjae Jeon <linkinjeon@gmail.com>
prev parent reply other threads:[~2012-04-08 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 12:27 [PATCH 1/2] [SCSI] ufs: update Response UPIU length in dword Santosh Y
2012-04-06 12:27 ` [PATCH 2/2] [SCSI] ufs: calculate read/write xfer len from cdb Santosh Y
2012-04-08 7:46 ` Namjae Jeon
2012-04-08 8:44 ` James Bottomley
2012-04-08 11:04 ` Santosh Y
2012-04-08 7:00 ` Namjae Jeon [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='CAKYAXd-_VQRCVeB6TsvL17=ZfCnafcmj++HBi-xfT7k4cGGC-w@mail.gmail.com' \
--to=linkinjeon@gmail.com \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=santoshsy@gmail.com \
--cc=vinholikatti@gmail.com \
--cc=yoshitake.kobayashi@toshiba.co.jp \
/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).