From: "Chanho Park" <chanho61.park@samsung.com>
To: <daejun7.park@samsung.com>,
"'ALIM AKHTAR'" <alim.akhtar@samsung.com>, <avri.altman@wdc.com>,
<jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<beanhuo@micron.com>, <bvanassche@acm.org>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] scsi: ufs: Fix referencing invalid rsp field
Date: Thu, 19 May 2022 15:46:32 +0900 [thread overview]
Message-ID: <000001d86b4c$2d460640$87d212c0$@samsung.com> (raw)
In-Reply-To: <252651381.41652940482659.JavaMail.epsvc@epcpadp4>
> This is a patch for fixing referencing sense data when it is invalid.
> When the length of the data segment is 0, there is no valid information in
> the rsp field, so ufshpb_rsp_upiu() is returned without additional
> operation.
>
You should put a proper fix tag to be applied the corresponding stable tree.
See https://www.kernel.org/doc/html/latest/process/submitting-patches.html
Fixes: 4b5f49079c52 ("scsi: ufs: ufshpb: L2P map management for HPB read")
Best Regards,
Chanho Park
> Signed-off-by: Daejun Park <daejun7.park@samsung.com>
> ---
> drivers/scsi/ufs/ufshpb.c | 19 +++++++------------
> 1 file changed, 7 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/scsi/ufs/ufshpb.c b/drivers/scsi/ufs/ufshpb.c index
> f1f65383e97d..8882b47f76d3 100644
> --- a/drivers/scsi/ufs/ufshpb.c
> +++ b/drivers/scsi/ufs/ufshpb.c
> @@ -1304,6 +1304,13 @@ void ufshpb_rsp_upiu(struct ufs_hba *hba, struct
> ufshcd_lrb *lrbp)
> struct utp_hpb_rsp *rsp_field = &lrbp->ucd_rsp_ptr->hr;
> int data_seg_len;
>
> + data_seg_len = be32_to_cpu(lrbp->ucd_rsp_ptr->header.dword_2)
> + & MASK_RSP_UPIU_DATA_SEG_LEN;
> +
> + /* If data segment length is zero, rsp_field is not valid */
> + if (!data_seg_len)
> + return;
> +
> if (unlikely(lrbp->lun != rsp_field->lun)) {
> struct scsi_device *sdev;
> bool found = false;
> @@ -1338,18 +1345,6 @@ void ufshpb_rsp_upiu(struct ufs_hba *hba, struct
> ufshcd_lrb *lrbp)
> return;
> }
>
> - data_seg_len = be32_to_cpu(lrbp->ucd_rsp_ptr->header.dword_2)
> - & MASK_RSP_UPIU_DATA_SEG_LEN;
> -
> - /* To flush remained rsp_list, we queue the map_work task */
> - if (!data_seg_len) {
> - if (!ufshpb_is_general_lun(hpb->lun))
> - return;
> -
> - ufshpb_kick_map_work(hpb);
> - return;
> - }
> -
> BUILD_BUG_ON(sizeof(struct utp_hpb_rsp) != UTP_HPB_RSP_SIZE);
>
> if (!ufshpb_is_hpb_rsp_valid(hba, lrbp, rsp_field))
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-05-19 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220519060529epcms2p8941ce10ed8cfb50c142140f1f69f8612@epcms2p8>
2022-05-19 6:05 ` [PATCH] scsi: ufs: Fix referencing invalid rsp field Daejun Park
2022-05-19 6:37 ` Avri Altman
2022-05-19 6:46 ` Chanho Park [this message]
2022-05-20 1:08 ` Martin K. Petersen
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='000001d86b4c$2d460640$87d212c0$@samsung.com' \
--to=chanho61.park@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=daejun7.park@samsung.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox