From: Shuah Khan <skhan@linuxfoundation.org>
To: Zhu Jun <zhujun2@cmss.chinamobile.com>,
jolsa@kernel.org, shuah@kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
eddyz87@gmail.com, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, mykolal@fb.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH bpf-next v2] selftests/bpf:fix a resource leak
Date: Wed, 10 Jul 2024 09:30:04 -0600 [thread overview]
Message-ID: <273183c9-101c-422b-9fcd-a9921c127cb1@linuxfoundation.org> (raw)
In-Reply-To: <20240710015913.2554-1-zhujun2@cmss.chinamobile.com>
On 7/9/24 19:59, Zhu Jun wrote:
> The requested resources should be closed before return
> in main(), otherwise resource leak will occur
>
> Signed-off-by: Zhu Jun <zhujun2@cmss.chinamobile.com>
How did you find this problem? Please give more details
on the tool used including the output from the tool.
> ---
> Changes in v2:
> - check for cg_fd >= 0 and have just one out label
>
> tools/testing/selftests/bpf/test_sockmap.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/tools/testing/selftests/bpf/test_sockmap.c b/tools/testing/selftests/bpf/test_sockmap.c
> index a34e95040994..285a9a714666 100644
> --- a/tools/testing/selftests/bpf/test_sockmap.c
> +++ b/tools/testing/selftests/bpf/test_sockmap.c
> @@ -2075,8 +2075,10 @@ int main(int argc, char **argv)
>
> if (!cg_fd) {
> cg_fd = cgroup_setup_and_join(CG_PATH);
> - if (cg_fd < 0)
> - return cg_fd;
> + if (cg_fd < 0) {
> + err = cg_fd;
> + goto out;
> + }
I don't this this improves the code - it makes it more complex.
If you want to improve this - add the same error message that
gets printed out for
case 'c':
in argument parsing.
fprintf(stderr, "ERROR: (%i) open cg path failed: %s\n",
cg_fd, optarg);
> cg_created = 1;
> }
>
> @@ -2092,7 +2094,7 @@ int main(int argc, char **argv)
> if (err) {
> fprintf(stderr, "populate program: (%s) %s\n",
> bpf_file, strerror(errno));
> - return 1;
> + goto out;
This looks good to me.
> }
> running = 1;
>
> @@ -2109,7 +2111,8 @@ int main(int argc, char **argv)
> free(options.whitelist);
> if (options.blacklist)
> free(options.blacklist);
> - close(cg_fd);
> + if (cg_fd >= 0)
Why is this check necessary?
> + close(cg_fd);
> if (cg_created)
> cleanup_cgroup_environment();
> return err;
thanks,
-- Shuah
prev parent reply other threads:[~2024-07-10 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 1:59 [PATCH bpf-next v2] selftests/bpf:fix a resource leak Zhu Jun
2024-07-10 15:30 ` Shuah Khan [this message]
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=273183c9-101c-422b-9fcd-a9921c127cb1@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
--cc=zhujun2@cmss.chinamobile.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