All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	clang-built-linux@googlegroups.com,
	Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH] ACPI / sysfs: Restructure get_status
Date: Mon, 11 Mar 2019 23:46:14 +0100	[thread overview]
Message-ID: <1766077.IDCbULq7Lr@aspire.rjw.lan> (raw)
In-Reply-To: <20190307173802.3448-1-natechancellor@gmail.com>

On Thursday, March 7, 2019 6:38:02 PM CET Nathan Chancellor wrote:
> When building with -Wsometimes-uninitialized, Clang warns:
> 
> drivers/acpi/sysfs.c:667:13: warning: variable 'result' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
> 
> Clang can't determine that all cases are covered by the two separate if
> statements. We could combine then to look like this:
> 
>     int result;
> 
>     if (...) {
>         ...
>     } else if {
>         ...
>     } else {
>         result -EINVAL;
>     }
> 
>     return result;
> 
> However, at that point, we can further simplify this function by only
> using result when absolutely needed and just direct returning the value
> of the function.
> 
> Link: https://github.com/ClangBuiltLinux/linux/issues/388
> Suggested-by: Nick Desaulniers <ndesaulniers@google.com>
> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
> ---
>  drivers/acpi/sysfs.c | 13 ++++---------
>  1 file changed, 4 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/acpi/sysfs.c b/drivers/acpi/sysfs.c
> index 41324f0b1bee..6ed785cadad9 100644
> --- a/drivers/acpi/sysfs.c
> +++ b/drivers/acpi/sysfs.c
> @@ -651,23 +651,18 @@ static void acpi_global_event_handler(u32 event_type, acpi_handle device,
>  static int get_status(u32 index, acpi_event_status *status,
>  		      acpi_handle *handle)
>  {
> -	int result;
> -
> -	if (index >= num_gpes + ACPI_NUM_FIXED_EVENTS)
> -		return -EINVAL;
> -
>  	if (index < num_gpes) {
> -		result = acpi_get_gpe_device(index, handle);
> +		int result = acpi_get_gpe_device(index, handle);
>  		if (result) {
>  			ACPI_EXCEPTION((AE_INFO, AE_NOT_FOUND,
>  					"Invalid GPE 0x%x", index));
>  			return result;
>  		}
> -		result = acpi_get_gpe_status(*handle, index, status);
> +		return acpi_get_gpe_status(*handle, index, status);
>  	} else if (index < (num_gpes + ACPI_NUM_FIXED_EVENTS))

In principle, it would suffice to replace the "else if (...)" with "else"
to fix the Clang warning AFAICS, but that's not the only issue with this
function.

> -		result = acpi_get_event_status(index - num_gpes, status);
> +		return acpi_get_event_status(index - num_gpes, status);
>  
> -	return result;
> +	return -EINVAL;
>  }
>  
>  static ssize_t counter_show(struct kobject *kobj,

Namely, it confuses errno with acpi_status and may cause the latter to be
returned to user space in certain situations which should never be done.

So, I'd prefer to apply something like the (untested so far) patch below.

---
 drivers/acpi/sysfs.c |   27 ++++++++++++++-------------
 1 file changed, 14 insertions(+), 13 deletions(-)

Index: linux-pm/drivers/acpi/sysfs.c
===================================================================
--- linux-pm.orig/drivers/acpi/sysfs.c
+++ linux-pm/drivers/acpi/sysfs.c
@@ -648,26 +648,27 @@ static void acpi_global_event_handler(u3
 	}
 }
 
-static int get_status(u32 index, acpi_event_status *status,
+static int get_status(u32 index, acpi_event_status *ret,
 		      acpi_handle *handle)
 {
-	int result;
+	acpi_status status;
 
 	if (index >= num_gpes + ACPI_NUM_FIXED_EVENTS)
 		return -EINVAL;
 
-	if (index < num_gpes) {
-		result = acpi_get_gpe_device(index, handle);
-		if (result) {
-			ACPI_EXCEPTION((AE_INFO, AE_NOT_FOUND,
-					"Invalid GPE 0x%x", index));
-			return result;
-		}
-		result = acpi_get_gpe_status(*handle, index, status);
-	} else if (index < (num_gpes + ACPI_NUM_FIXED_EVENTS))
-		result = acpi_get_event_status(index - num_gpes, status);
+	if (index >= num_gpes)
+		return acpi_get_event_status(index - num_gpes, ret);
 
-	return result;
+	status = acpi_get_gpe_device(index, handle);
+	if (ACPI_FAILURE(status)) {
+		ACPI_EXCEPTION((AE_INFO, AE_NOT_FOUND, "Invalid GPE 0x%x", index));
+		return -ENXIO;
+	}
+	status = acpi_get_gpe_status(*handle, index, ret);
+	if (ACPI_FAILURE(status))
+		return -EIO;
+
+	return 0;
 }
 
 static ssize_t counter_show(struct kobject *kobj,

  parent reply	other threads:[~2019-03-11 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 17:38 [PATCH] ACPI / sysfs: Restructure get_status Nathan Chancellor
2019-03-07 18:21 ` Nick Desaulniers
2019-03-11 22:46 ` Rafael J. Wysocki [this message]
2019-03-11 22:56   ` Rafael J. Wysocki
2019-03-12  0:07     ` Nathan Chancellor

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=1766077.IDCbULq7Lr@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=clang-built-linux@googlegroups.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=natechancellor@gmail.com \
    --cc=ndesaulniers@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.