From: Bart Van Assche <bvanassche@acm.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Bean Huo" <beanhuo@micron.com>,
stable@vger.kernel.org,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Peter Wang" <peter.wang@mediatek.com>,
"Avri Altman" <avri.altman@wdc.com>,
"Maramaina Naresh" <quic_mnaresh@quicinc.com>,
"Mike Bi" <mikebi@micron.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Luca Porzio" <lporzio@micron.com>
Subject: Re: [PATCH] scsi: ufs: Start the RTC update work later
Date: Fri, 1 Nov 2024 09:31:27 -0700 [thread overview]
Message-ID: <116df065-ab9a-46e2-90eb-9ae5f5f01b70@acm.org> (raw)
In-Reply-To: <20241101075309.wvfv2fcjeuimcihj@thinkpad>
On 11/1/24 12:53 AM, Manivannan Sadhasivam wrote:
> On Thu, Oct 31, 2024 at 02:26:24PM -0700, Bart Van Assche wrote:
>> The RTC update work involves runtime resuming the UFS controller. Hence,
>> only start the RTC update work after runtime power management in the UFS
>> driver has been fully initialized. This patch fixes the following kernel
>> crash:
>>
>> Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
>> Workqueue: events ufshcd_rtc_work
>> Call trace:
>> _raw_spin_lock_irqsave+0x34/0x8c (P)
>> pm_runtime_get_if_active+0x24/0x9c (L)
>> pm_runtime_get_if_active+0x24/0x9c
>> ufshcd_rtc_work+0x138/0x1b4
>> process_one_work+0x148/0x288
>> worker_thread+0x2cc/0x3d4
>> kthread+0x110/0x114
>> ret_from_fork+0x10/0x20
>>
>> Reported-by: Neil Armstrong <neil.armstrong@linaro.org>
>> Closes: https://lore.kernel.org/linux-scsi/0c0bc528-fdc2-4106-bc99-f23ae377f6f5@linaro.org/
>> Fixes: 6bf999e0eb41 ("scsi: ufs: core: Add UFS RTC support")
>> Cc: Bean Huo <beanhuo@micron.com>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
>
> Bart, Thanks for the fix! While looking into this patch, I also found the
> weirdness of the ufshcd_rpm_*() helpers in ufshcd-priv.h. Their naming doesn't
> seem to indicate whether those helpers are for WLUN or for HBA. Also, I don't
> see the benefit of these helpers since they just wrap generic pm_runtime*
> calls. Then there are other open coding instances in the ufshcd.c. Like
>
> pm_runtime_suspended(&hba->ufs_device_wlun->sdev_gendev)
> pm_runtime_set_active(&hba->ufs_device_wlun->sdev_gendev)
>
> Moreover, we do check for the presence of hba->ufs_device_wlun before calling
> ufshcd_rpm_get_sync() in ufshcd_remove(). This could be one other way to fix
> this null ptr dereference even though I wouldn't recommend doing so as calling
> rtc_work early is pointless.
>
> So I think we should remove these helpers to avoid having these discrepancies.
> WDYT?
Hi Manivannan,
In the context of the Linux kernel, in general, one-line helper
functions are considered questionable. In this case I prefer to keep the
helper functions since these encapsulate an implementation detail,
namely that the WLUN sdev_gendev member is used to control runtime power
management of the UFS host controller.
Checking whether or not the hba->ufs_device_wlun pointer is NULL from
the ufshcd_rtc_work() function would be racy since that pointer is
modified from another thread. So I prefer the patch at the start of this
thread instead of adding a hba->ufs_device_wlun pointer check.
Thanks,
Bart.
next prev parent reply other threads:[~2024-11-01 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 21:26 [PATCH] scsi: ufs: Start the RTC update work later Bart Van Assche
2024-11-01 6:27 ` Peter Wang (王信友)
2024-11-01 7:53 ` Manivannan Sadhasivam
2024-11-01 16:31 ` Bart Van Assche [this message]
2024-11-02 10:21 ` Manivannan Sadhasivam
2024-11-01 21:03 ` Bean Huo
2024-11-04 13:43 ` Neil Armstrong
2024-11-05 2:31 ` Martin K. Petersen
2024-11-05 3:48 ` James Bottomley
2024-11-05 18:54 ` Bart Van Assche
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=116df065-ab9a-46e2-90eb-9ae5f5f01b70@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=lporzio@micron.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=martin.petersen@oracle.com \
--cc=mikebi@micron.com \
--cc=neil.armstrong@linaro.org \
--cc=peter.wang@mediatek.com \
--cc=quic_mnaresh@quicinc.com \
--cc=stable@vger.kernel.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