public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>, james.morse@arm.com
Cc: Hanjun Guo <guohanjun@huawei.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	kernel@pengutronix.de
Subject: Re: [PATCH] ACPI: AGDI: Improve error reporting for problems during .remove()
Date: Tue, 18 Oct 2022 11:35:04 +0200	[thread overview]
Message-ID: <Y05zSNDbt94ejpzm@lpieralisi> (raw)
In-Reply-To: <20221014160623.467195-1-u.kleine-koenig@pengutronix.de>

[+James]

On Fri, Oct 14, 2022 at 06:06:23PM +0200, Uwe Kleine-König wrote:
> Returning an error value in a platform driver's remove callback results in
> a generic error message being emitted by the driver core, but otherwise it
> doesn't make a difference. The device goes away anyhow.
> 
> So instead of triggering the generic platform error message, emit a more
> helpful message if a problem occurs and return 0 to suppress the generic
> message.
> 
> This patch is a preparation for making platform remove callbacks return
> void.

If that's the plan - I don't have anything against this patch.

> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Hello,
> 
> note that in the situations where the driver returned an error before
> and now emits a message, there is a resource leak. Someone who knows
> more about this driver and maybe even can test stuff, might want to
> address this. This might not only be about non-freed memory, the device
> disappears but it is kept in sdei_list and so might be used after being
> gone.

I'd need James' input on this. I guess we may ignore
sdei_event_disable() return value and continue anyway in agdi_remove(),
whether that's the right thing to do it is a different question.

Lorenzo

> Best regards
> Uwe
> 
>  drivers/acpi/arm64/agdi.c | 13 ++++++++++---
>  1 file changed, 10 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/acpi/arm64/agdi.c b/drivers/acpi/arm64/agdi.c
> index cf31abd0ed1b..f605302395c3 100644
> --- a/drivers/acpi/arm64/agdi.c
> +++ b/drivers/acpi/arm64/agdi.c
> @@ -64,8 +64,11 @@ static int agdi_remove(struct platform_device *pdev)
>  	int err, i;
>  
>  	err = sdei_event_disable(adata->sdei_event);
> -	if (err)
> -		return err;
> +	if (err) {
> +		dev_err(&pdev->dev, "Failed to disable sdei-event #%d (%pe)\n",
> +			adata->sdei_event, ERR_PTR(err));
> +		return 0;
> +	}
>  
>  	for (i = 0; i < 3; i++) {
>  		err = sdei_event_unregister(adata->sdei_event);
> @@ -75,7 +78,11 @@ static int agdi_remove(struct platform_device *pdev)
>  		schedule();
>  	}
>  
> -	return err;
> +	if (err)
> +		dev_err(&pdev->dev, "Failed to unregister sdei-event #%d (%pe)\n",
> +			adata->sdei_event, ERR_PTR(err));
> +
> +	return 0;
>  }
>  
>  static struct platform_driver agdi_driver = {
> 
> base-commit: 4fe89d07dcc2804c8b562f6c7896a45643d34b2f
> -- 
> 2.37.2
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-10-18  9:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 16:06 [PATCH] ACPI: AGDI: Improve error reporting for problems during .remove() Uwe Kleine-König
2022-10-18  9:35 ` Lorenzo Pieralisi [this message]
2022-10-26 16:09   ` James Morse
2022-10-26 17:23     ` Uwe Kleine-König
2022-12-19 22:18       ` Uwe Kleine-König
2023-02-14 16:36         ` Uwe Kleine-König
2023-04-12 16:24           ` Uwe Kleine-König
2023-04-13  8:23     ` Lorenzo Pieralisi
2023-04-13 14:48       ` Will Deacon
2023-04-17 15:03 ` Will Deacon

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=Y05zSNDbt94ejpzm@lpieralisi \
    --to=lpieralisi@kernel.org \
    --cc=guohanjun@huawei.com \
    --cc=james.morse@arm.com \
    --cc=kernel@pengutronix.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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