From: Bart Van Assche <bvanassche@acm.org>
To: Miles Chen <miles.chen@mediatek.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Martin Kepplinger <martink@posteo.de>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, wsd_upstream@mediatek.com,
Stanley Chu <stanley.chu@mediatek.com>
Subject: Re: [PATCH] scsi: sd: fix crashes in sd_resume_runtime
Date: Fri, 15 Oct 2021 10:54:36 -0700 [thread overview]
Message-ID: <fe7bacf4-aa9a-6742-8382-a7c9b31236a7@acm.org> (raw)
In-Reply-To: <20211015074654.19615-1-miles.chen@mediatek.com>
On 10/15/21 00:46, Miles Chen wrote:
> Crash:
> [ 4.695171][ T151] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008
> [ 4.710577][ T151] Internal error: Oops: 96000005 [#1] PREEMPT SMP
> [ 4.856708][ T151] die+0x16c/0x59c
> [ 4.857191][ T151] __do_kernel_fault+0x1e8/0x210
> [ 4.857833][ T151] do_page_fault+0xa4/0x654
> [ 4.858418][ T151] do_translation_fault+0x6c/0x1b0
> [ 4.859083][ T151] do_mem_abort+0x68/0x10c
> [ 4.859655][ T151] el1_abort+0x40/0x64
> [ 4.860182][ T151] el1h_64_sync_handler+0x54/0x88
> [ 4.860834][ T151] el1h_64_sync+0x7c/0x80
> [ 4.861395][ T151] sd_resume_runtime+0x20/0x14c
> [ 4.862025][ T151] scsi_runtime_resume+0x84/0xe4
> [ 4.862667][ T151] __rpm_callback+0x1f4/0x8cc
> [ 4.863275][ T151] rpm_resume+0x7e8/0xaa4
> [ 4.863836][ T151] __pm_runtime_resume+0xa0/0x110
> [ 4.864489][ T151] sd_probe+0x30/0x428
> [ 4.865016][ T151] really_probe+0x14c/0x500
> [ 4.865602][ T151] __driver_probe_device+0xb4/0x18c
> [ 4.866278][ T151] driver_probe_device+0x60/0x2c4
> [ 4.866931][ T151] __device_attach_driver+0x228/0x2bc
> [ 4.867630][ T151] __device_attach_async_helper+0x154/0x21c
> [ 4.868398][ T151] async_run_entry_fn+0x5c/0x1c4
> [ 4.869038][ T151] process_one_work+0x3ac/0x590
> [ 4.869670][ T151] worker_thread+0x320/0x758
> [ 4.870265][ T151] kthread+0x2e8/0x35c
> [ 4.870792][ T151] ret_from_fork+0x10/0x20
>
> Cc: Stanley Chu <stanley.chu@mediatek.com>
> Fixes: ed4246d37f3b ("scsi: sd: REQUEST SENSE for BLIST_IGN_MEDIA_CHANGE devices in runtime_resume()")
> Signed-off-by: Miles Chen <miles.chen@mediatek.com>
> ---
> drivers/scsi/sd.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
> index 523bf2fdc253..fce63335084e 100644
> --- a/drivers/scsi/sd.c
> +++ b/drivers/scsi/sd.c
> @@ -3683,7 +3683,12 @@ static int sd_resume(struct device *dev)
> static int sd_resume_runtime(struct device *dev)
> {
> struct scsi_disk *sdkp = dev_get_drvdata(dev);
> - struct scsi_device *sdp = sdkp->device;
> + struct scsi_device *sdp;
> +
> + if (!sdkp) /* E.g.: runtime resume at the start of sd_probe() */
> + return 0;
> +
> + sdp = sdkp->device;
>
> if (sdp->ignore_media_change) {
> /* clear the device's sense data */
Fixing this crash by adding a check inside sd_resume_runtime() seems
wrong to me. sd_probe() namely calls dev_set_drvdata(dev, sdkp) before
sd_probe() has finished so even with the above patch applied sd_resume()
can be called before sd_probe() has finished.
With which kernel version has this crash been encountered? The
scsi_autopm_get_device() / scsi_autopm_put_device() pair added by commit
6fe8c1dbefd6 ("scsi: balance out autopm get/put calls in
scsi_sysfs_add_sdev()"; kernel v3.18) should be sufficient to prevent
the reported crash.
Thanks,
Bart.
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2021-10-15 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 7:46 [PATCH] scsi: sd: fix crashes in sd_resume_runtime Miles Chen
2021-10-15 7:55 ` Martin Kepplinger
2021-10-15 13:33 ` Stanley Chu
2021-10-15 17:54 ` Bart Van Assche [this message]
2021-10-15 20:11 ` miles.chen
2021-10-15 21:14 ` Bart Van Assche
2021-10-15 23:18 ` Miles Chen
2021-10-19 3:43 ` 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=fe7bacf4-aa9a-6742-8382-a7c9b31236a7@acm.org \
--to=bvanassche@acm.org \
--cc=jejb@linux.ibm.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=martin.petersen@oracle.com \
--cc=martink@posteo.de \
--cc=matthias.bgg@gmail.com \
--cc=miles.chen@mediatek.com \
--cc=stanley.chu@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