From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: nguyenb@codeaurora.org, kernel-team@android.com,
ziqichen@codeaurora.org, asutoshd@codeaurora.org,
Can Guo <cang@codeaurora.org>,
hongwus@codeaurora.org, linux-scsi@vger.kernel.org
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
open list <linux-kernel@vger.kernel.org>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
Stanley Chu <stanley.chu@mediatek.com>,
Avri Altman <avri.altman@wdc.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Jaegeuk Kim <jaegeuk@kernel.org>, Bean Huo <beanhuo@micron.com>
Subject: Re: [PATCH v3] scsi: ufs: Fix a possible use before initialization case
Date: Tue, 15 Jun 2021 23:48:51 -0400 [thread overview]
Message-ID: <162381524896.11966.2627984284805294316.b4-ty@oracle.com> (raw)
In-Reply-To: <1623227044-22635-1-git-send-email-cang@codeaurora.org>
On Wed, 9 Jun 2021 01:24:00 -0700, Can Guo wrote:
> In ufshcd_exec_dev_cmd(), if error happens before lrpb is initialized,
> then we should bail out instead of letting trace record the error.
Applied to 5.14/scsi-queue, thanks!
[1/1] scsi: ufs: Fix a possible use before initialization case
https://git.kernel.org/mkp/scsi/c/eb783bb8bbe7
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2021-06-16 3:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 8:24 [PATCH v3] scsi: ufs: Fix a possible use before initialization case Can Guo
2021-06-09 17:26 ` Nathan Chancellor
2021-06-10 2:56 ` Martin K. Petersen
2021-06-16 3:48 ` 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=162381524896.11966.2627984284805294316.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=cang@codeaurora.org \
--cc=hongwus@codeaurora.org \
--cc=jaegeuk@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nguyenb@codeaurora.org \
--cc=stanley.chu@mediatek.com \
--cc=ziqichen@codeaurora.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;
as well as URLs for NNTP newsgroup(s).