From: Icenowy Zheng <zhengxingda@iscas.ac.cn>
To: Myeonghun Pak <mhun512@gmail.com>, dri-devel@lists.freedesktop.org
Cc: Sui Jingfeng <suijingfeng@loongson.cn>,
Jianmin Lv <lvjianmin@loongson.cn>,
Qianhai Wu <wuqianhai@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
Mingcong Bai <jeffbai@aosc.io>, Xi Ruoyao <xry111@xry111.site>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Ijae Kim <ae878000@gmail.com>
Subject: Re: [PATCH] drm/loongson: clean up KMS polling on probe failure
Date: Tue, 12 May 2026 01:22:41 +0800 [thread overview]
Message-ID: <3ee00ebc4ff5bcf2a8754466f8d9d04b24f81858.camel@iscas.ac.cn> (raw)
In-Reply-To: <20260511170152.16957-1-mhun512@gmail.com>
在 2026-05-12二的 02:01 +0900,Myeonghun Pak写道:
> lsdc_pci_probe() initializes KMS polling before setting up vblank
> support,
> requesting the IRQ and registering the DRM device. If any of those
> later
> steps fails, probe returns without finalizing polling. The remove
> path has
> the same lifetime gap when tearing down a successfully registered
> device.
>
> Route those probe failures through a poll cleanup label. Also
> finalize
> polling from remove before unregistering the DRM device.
Interesting, but it looks like a `drmm_kms_helper_poll_init` function
exists (while rarely used).
Maybe it's better to switch to this? Or maybe there's some reason not
to use this?
Thanks,
Icenowy
>
> This issue was identified during our ongoing static-analysis research
> while
> reviewing kernel code.
>
> Fixes: f39db26c5428 ("drm: Add kms driver for loongson display
> controller")
> Cc: stable@vger.kernel.org
> Co-developed-by: Ijae Kim <ae878000@gmail.com>
> Signed-off-by: Ijae Kim <ae878000@gmail.com>
> Signed-off-by: Myeonghun Pak <mhun512@gmail.com>
> ---
> drivers/gpu/drm/loongson/lsdc_drv.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/loongson/lsdc_drv.c
> b/drivers/gpu/drm/loongson/lsdc_drv.c
> index abf5bf68ee..3db1f8690a 100644
> --- a/drivers/gpu/drm/loongson/lsdc_drv.c
> +++ b/drivers/gpu/drm/loongson/lsdc_drv.c
> @@ -297,7 +297,7 @@ static int lsdc_pci_probe(struct pci_dev *pdev,
> const struct pci_device_id *ent)
> if (loongson_vblank) {
> ret = drm_vblank_init(ddev, descp->num_of_crtc);
> if (ret)
> - return ret;
> + goto err_poll_fini;
>
> ret = devm_request_irq(&pdev->dev, pdev->irq,
> descp->funcs->irq_handler,
> @@ -305,7 +305,7 @@ static int lsdc_pci_probe(struct pci_dev *pdev,
> const struct pci_device_id *ent)
> dev_name(&pdev->dev), ddev);
> if (ret) {
> drm_err(ddev, "Failed to register interrupt:
> %d\n", ret);
> - return ret;
> + goto err_poll_fini;
> }
>
> drm_info(ddev, "registered irq: %u\n", pdev->irq);
> @@ -313,17 +313,22 @@ static int lsdc_pci_probe(struct pci_dev *pdev,
> const struct pci_device_id *ent)
>
> ret = drm_dev_register(ddev, 0);
> if (ret)
> - return ret;
> + goto err_poll_fini;
>
> drm_client_setup(ddev, NULL);
>
> return 0;
> +
> +err_poll_fini:
> + drm_kms_helper_poll_fini(ddev);
> + return ret;
> }
>
> static void lsdc_pci_remove(struct pci_dev *pdev)
> {
> struct drm_device *ddev = pci_get_drvdata(pdev);
>
> + drm_kms_helper_poll_fini(ddev);
> drm_dev_unregister(ddev);
> drm_atomic_helper_shutdown(ddev);
> }
next prev parent reply other threads:[~2026-05-11 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 17:01 [PATCH] drm/loongson: clean up KMS polling on probe failure Myeonghun Pak
2026-05-11 17:22 ` Icenowy Zheng [this message]
2026-05-12 6:26 ` Thomas Zimmermann
2026-05-12 6:35 ` Myeonghun Pak
2026-05-16 4:50 ` Claude review: " Claude Code Review Bot
2026-05-16 4:50 ` Claude Code Review Bot
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=3ee00ebc4ff5bcf2a8754466f8d9d04b24f81858.camel@iscas.ac.cn \
--to=zhengxingda@iscas.ac.cn \
--cc=ae878000@gmail.com \
--cc=airlied@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeffbai@aosc.io \
--cc=linux-kernel@vger.kernel.org \
--cc=lvjianmin@loongson.cn \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mhun512@gmail.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=suijingfeng@loongson.cn \
--cc=tzimmermann@suse.de \
--cc=wuqianhai@loongson.cn \
--cc=xry111@xry111.site \
/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