From: Bart Van Assche <bvanassche@acm.org>
To: "Peter Wang (王信友)" <peter.wang@mediatek.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"chullee@google.com" <chullee@google.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"avri.altman@sandisk.com" <avri.altman@sandisk.com>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"quic_nguyenb@quicinc.com" <quic_nguyenb@quicinc.com>,
"beanhuo@micron.com" <beanhuo@micron.com>
Subject: Re: [PATCH 1/8] ufs: core: Fix a race condition related to the "hid" attribute group
Date: Fri, 17 Oct 2025 09:25:51 -0700 [thread overview]
Message-ID: <569fcd05-4d77-468a-bc8d-c86d0a5dfc8c@acm.org> (raw)
In-Reply-To: <22dd7d580444be92d0029694468cdddf1ac98f13.camel@mediatek.com>
On 10/17/25 1:27 AM, Peter Wang (王信友) wrote:
> How does the sysfs_update_group() call happen from the context
> of the thread that executes ufshcd_async_scan()?
> Do you have a backtrace?
Sure. The call chain is as follows:
ufshcd_async_scan()
ufshcd_probe_hba(hba, true)
ufshcd_device_init()
ufshcd_device_params_init()
ufs_get_device_desc()
sysfs_update_group()
Please note that this call chain is only taken if the following quirk
has been set: UFSHCD_QUIRK_REINIT_AFTER_MAX_GEAR_SWITCH.
Thanks,
Bart.
next prev parent reply other threads:[~2025-10-17 16:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 20:00 [PATCH 0/8] Eight small UFS patches Bart Van Assche
2025-10-14 20:00 ` [PATCH 1/8] ufs: core: Fix a race condition related to the "hid" attribute group Bart Van Assche
2025-10-15 22:24 ` Bart Van Assche
2025-10-17 8:27 ` Peter Wang (王信友)
2025-10-17 16:25 ` Bart Van Assche [this message]
2025-10-20 6:51 ` Peter Wang (王信友)
2025-10-20 16:13 ` Bart Van Assche
2025-10-21 3:04 ` Peter Wang (王信友)
2025-10-21 15:01 ` Bart Van Assche
2025-10-22 12:39 ` Peter Wang (王信友)
2025-10-27 14:04 ` Neil Armstrong
2025-10-27 17:12 ` Bart Van Assche
2025-10-14 20:00 ` [PATCH 2/8] ufs: core: Reduce link startup failure logging Bart Van Assche
2025-10-14 20:00 ` [PATCH 3/8] ufs: core: Improve documentation in include/ufs/ufshci.h Bart Van Assche
2025-10-14 20:00 ` [PATCH 4/8] ufs: core: Change the type of uic_command::cmd_active Bart Van Assche
2025-10-14 20:00 ` [PATCH 5/8] ufs: core: Remove UFS_DEV_COMP Bart Van Assche
2025-10-17 8:28 ` Peter Wang (王信友)
2025-10-14 20:00 ` [PATCH 6/8] ufs: core: Move the ufshcd_enable_intr() declaration Bart Van Assche
2025-10-17 8:29 ` Peter Wang (王信友)
2025-10-14 20:00 ` [PATCH 7/8] ufs: core: Remove a goto label from ufshcd_uic_cmd_compl() Bart Van Assche
2025-10-17 8:29 ` Peter Wang (王信友)
2025-10-14 20:01 ` [PATCH 8/8] ufs: core: Simplify ufshcd_mcq_sq_cleanup() using guard() Bart Van Assche
2025-10-17 8:30 ` Peter Wang (王信友)
2025-10-22 2:13 ` [PATCH 0/8] Eight small UFS patches Martin K. Petersen
2025-10-22 11:04 ` Manivannan Sadhasivam
2025-10-22 16:59 ` Bart Van Assche
2025-10-22 17:31 ` Manivannan Sadhasivam
2025-10-23 17:29 ` Bart Van Assche
2025-10-24 2:16 ` 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=569fcd05-4d77-468a-bc8d-c86d0a5dfc8c@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=adrian.hunter@intel.com \
--cc=avri.altman@sandisk.com \
--cc=beanhuo@micron.com \
--cc=chullee@google.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=peter.wang@mediatek.com \
--cc=quic_nguyenb@quicinc.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;
as well as URLs for NNTP newsgroup(s).