From: <peter.wang@mediatek.com>
To: <linux-scsi@vger.kernel.org>, <martin.petersen@oracle.com>,
<avri.altman@wdc.com>, <alim.akhtar@samsung.com>,
<jejb@linux.ibm.com>
Cc: <wsd_upstream@mediatek.com>, <linux-mediatek@lists.infradead.org>,
<peter.wang@mediatek.com>, <chun-hung.wu@mediatek.com>,
<alice.chao@mediatek.com>, <cc.chou@mediatek.com>,
<chaotian.jing@mediatek.com>, <jiajie.hao@mediatek.com>,
<powen.kao@mediatek.com>, <qilin.tan@mediatek.com>,
<lin.gui@mediatek.com>, <tun-yu.yu@mediatek.com>,
<eddie.huang@mediatek.com>, <naomi.chu@mediatek.com>,
<chu.stanley@gmail.com>
Subject: [PATCH v3 0/2] ufs: core: fix ufshcd_abort_all racing issue
Date: Fri, 28 Jun 2024 15:00:28 +0800 [thread overview]
Message-ID: <20240628070030.30929-1-peter.wang@mediatek.com> (raw)
From: Peter Wang <peter.wang@mediatek.com>
This series fixes race condition KE in ufshcd_err_handler, which call
ufshcd_abort_all abort an already completed request by ISR in MCQ mode.
V3:
- Modify ufshcd_mcq_req_to_hwq to distinguish cmd is completed or not
- Split two patches and add more race description.
V2:
- Change patch description and add Fixes/Cc tag
Peter Wang (2):
ufs: core: fix ufshcd_clear_cmd racing issue
ufs: core: fix ufshcd_abort_one racing issue
drivers/ufs/core/ufs-mcq.c | 11 ++++++-----
drivers/ufs/core/ufshcd.c | 2 ++
2 files changed, 8 insertions(+), 5 deletions(-)
--
2.18.0
next reply other threads:[~2024-06-28 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 7:00 peter.wang [this message]
2024-06-28 7:00 ` [PATCH v3 1/2] ufs: core: fix ufshcd_clear_cmd racing issue peter.wang
2024-06-28 19:25 ` Bart Van Assche
2024-06-28 7:00 ` [PATCH v3 2/2] ufs: core: fix ufshcd_abort_one " peter.wang
2024-06-28 19:26 ` Bart Van Assche
2024-07-05 3:56 ` [PATCH v3 0/2] ufs: core: fix ufshcd_abort_all " 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=20240628070030.30929-1-peter.wang@mediatek.com \
--to=peter.wang@mediatek.com \
--cc=alice.chao@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=cc.chou@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=chu.stanley@gmail.com \
--cc=chun-hung.wu@mediatek.com \
--cc=eddie.huang@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=jiajie.hao@mediatek.com \
--cc=lin.gui@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=naomi.chu@mediatek.com \
--cc=powen.kao@mediatek.com \
--cc=qilin.tan@mediatek.com \
--cc=tun-yu.yu@mediatek.com \
--cc=wsd_upstream@mediatek.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