From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Avri Altman <avri.altman@wdc.com>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Evan Green <evgreen@chromium.org>, Bean Huo <beanhuo@micron.com>,
Pedro Sousa <pedrom.sousa@synopsys.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avi Shchislowski <avi.shchislowski@wdc.com>,
Alex Lemberg <alex.lemberg@wdc.com>
Subject: Re: [PATCH] scsi: ufs: Check that space was properly alloced in copy_query_response
Date: Tue, 04 Jun 2019 22:11:54 -0400 [thread overview]
Message-ID: <yq14l54srv9.fsf@oracle.com> (raw)
In-Reply-To: <1558427062-5084-1-git-send-email-avri.altman@wdc.com> (Avri Altman's message of "Tue, 21 May 2019 11:24:22 +0300")
Avri,
> struct ufs_dev_cmd is the main container that supports device management
> commands. In the case of a read descriptor request, we assume that the
> proper space was allocated in dev_cmd to hold the returning descriptor.
>
> This is no longer true, as there are flows that doesn't use dev_cmd
> for device management requests, and was wrong in the first place.
Applied to 5.2/scsi-fixes, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-06-05 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190521082527epcas1p44fe0c4659549ae265c9d59ef7844e57e@epcas1p4.samsung.com>
2019-05-21 8:24 ` [PATCH] scsi: ufs: Check that space was properly alloced in copy_query_response Avri Altman
2019-05-28 4:07 ` Alim Akhtar
2019-06-03 8:37 ` Avri Altman
2019-05-28 7:51 ` [EXT] " Bean Huo (beanhuo)
2019-06-05 2:11 ` Martin K. Petersen [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=yq14l54srv9.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=alex.lemberg@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=avi.shchislowski@wdc.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=evgreen@chromium.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pedrom.sousa@synopsys.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.