From: Shuah Khan <skhan@linuxfoundation.org>
To: Hao Zeng <zenghao@kylinos.cn>
Cc: trenn@suse.com, shuah@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3] cpupower:Fix resource leaks in sysfs_get_enabled()
Date: Mon, 17 Apr 2023 15:09:12 -0600 [thread overview]
Message-ID: <4eaae372-c312-6a77-f57f-dffc5f9aff02@linuxfoundation.org> (raw)
In-Reply-To: <20230417075617.10487-1-zenghao@kylinos.cn>
On 4/17/23 01:56, Hao Zeng wrote:
> The sysfs_get_enabled() opened file processor not closed,
> may cause a file handle leak.
> Putting error handling and resource cleanup code together
> makes the code easy to maintain and read.
> Removed the unnecessary else if branch from the original
> function, as it should return an error in cases other than '0'.
>
> Signed-off-by: Hao Zeng <zenghao@kylinos.cn>
> Suggested-by: Shuah Khan <skhan@linuxfoundation.org>
> ---
> tools/power/cpupower/lib/powercap.c | 22 ++++++++++++++--------
> 1 file changed, 14 insertions(+), 8 deletions(-)
>
> diff --git a/tools/power/cpupower/lib/powercap.c b/tools/power/cpupower/lib/powercap.c
> index 0ce29ee4c2e4..f0334a5f1acf 100644
> --- a/tools/power/cpupower/lib/powercap.c
> +++ b/tools/power/cpupower/lib/powercap.c
> @@ -40,25 +40,31 @@ static int sysfs_get_enabled(char *path, int *mode)
> {
> int fd;
> char yes_no;
> + int ret = 0;
>
> *mode = 0;
>
> fd = open(path, O_RDONLY);
> - if (fd == -1)
> - return -1;
> + if (fd == -1) {
> + ret = -1;
> + goto out;
> + }
>
> if (read(fd, &yes_no, 1) != 1) {
> - close(fd);
> - return -1;
> + ret = -1;
> + goto out_close;
> }
>
> if (yes_no == '1') {
> *mode = 1;
> - return 0;
You can just add goto out_close here
> - } else if (yes_no == '0') {
> - return 0;
Keep == '0' check and add goto out_close here
> + } else if (yes_no != '0') {
This can be just else with the above change.
> + ret = -1;
> + goto out_close;
> }
> - return -1;
> +out_close:
> + close(fd);
> +out:
> + return ret;
> }
>
> int powercap_get_enabled(int *mode)
thanks,
-- Shuah
next prev parent reply other threads:[~2023-04-17 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 7:56 Hao Zeng
2023-04-17 21:09 ` Shuah Khan [this message]
2023-04-18 2:21 ` Hao Zeng
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=4eaae372-c312-6a77-f57f-dffc5f9aff02@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=trenn@suse.com \
--cc=zenghao@kylinos.cn \
/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
all inboxes | Powered by JetHome®