From: Paolo Abeni <pabeni@redhat.com>
To: Liu Jing <liujing@cmss.chinamobile.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
shuah@kernel.org
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/net: missing close function in randomize function
Date: Tue, 09 Jul 2024 12:46:14 +0200 [thread overview]
Message-ID: <b2fe4035eb3b587657442490b1ce8410db63e5d2.camel@redhat.com> (raw)
In-Reply-To: <20240705082421.7061-1-liujing@cmss.chinamobile.com>
On Fri, 2024-07-05 at 16:24 +0800, Liu Jing wrote:
> in randomize function, there is a open function, but there is no
> close function in the randomize, which is easy to cause memory leaks.
Please not that the file descriptor is not leaked, the kernel will
dispose it at process exit() time.
>
> Signed-off-by: Liu Jing <liujing@cmss.chinamobile.com>
> ---
> tools/testing/selftests/net/tcp_mmap.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/testing/selftests/net/tcp_mmap.c b/tools/testing/selftests/net/tcp_mmap.c
> index 4fcce5150850..ab305e262d0a 100644
> --- a/tools/testing/selftests/net/tcp_mmap.c
> +++ b/tools/testing/selftests/net/tcp_mmap.c
> @@ -438,6 +438,7 @@ static void randomize(void *target, size_t count)
> perror("read /dev/urandom");
> exit(1);
> }
> + close(urandom);
> }
>
> int main(int argc, char *argv[])
This is outside any loop, so the overall effect WRT the self-test
itself is not visible.
I think we are better off without this kind of changes, unless they are
part of a largish re-factor.
Thanks,
Paolo
prev parent reply other threads:[~2024-07-09 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 8:24 Liu Jing
2024-07-09 10:46 ` Paolo Abeni [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=b2fe4035eb3b587657442490b1ce8410db63e5d2.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liujing@cmss.chinamobile.com \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
/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®