From: "Alex Bennée" <alex.bennee@linaro.org>
To: Alex Chen <alex.chen@huawei.com>
Cc: Thomas Huth <thuth@redhat.com>,
zhang.zhanghailiang@huawei.com, qemu-trivial@nongnu.org,
mjt@tls.msk.ru, Laurent Vivier <laurent@vivier.eu>,
qemu-devel@nongnu.org, zhengchuan@huawei.com
Subject: Re: [PATCH 2/2] plugins: Fix two resource leaks in connect_socket()
Date: Tue, 17 Nov 2020 11:35:12 +0000 [thread overview]
Message-ID: <87k0ukw70v.fsf@linaro.org> (raw)
In-Reply-To: <5FB3239E.6030709@huawei.com>
Alex Chen <alex.chen@huawei.com> writes:
> On 2020/11/17 0:50, Thomas Huth wrote:
>> On 28/10/2020 14.45, AlexChen wrote:
>>> Either accept() fails or exits normally, we need to close the fd.
>>>
>>> Reported-by: Euler Robot <euler.robot@huawei.com>
>>> Signed-off-by: AlexChen <alex.chen@huawei.com>
>>> ---
>>> contrib/plugins/lockstep.c | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/contrib/plugins/lockstep.c b/contrib/plugins/lockstep.c
>>> index 319bd44b83..5aad50869d 100644
>>> --- a/contrib/plugins/lockstep.c
>>> +++ b/contrib/plugins/lockstep.c
>>> @@ -268,11 +268,13 @@ static bool setup_socket(const char *path)
>>> socket_fd = accept(fd, NULL, NULL);
>>
>> I think you could also simply close(fd) here instead, then you don't have to
>> do it twice below.
>>
>
> Hi Thomas and Alex,
> Thanks for your suggestion. It's a simple and effective solution.
> Considering that the patch v3 has been queued by Alex Bennée,
> May I modify this patch and then send patch v4?
The fix has already been merged so a fresh patch would make more sense.
--
Alex Bennée
next prev parent reply other threads:[~2020-11-17 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 13:45 [PATCH 2/2] plugins: Fix two resource leaks in connect_socket() AlexChen
2020-11-05 6:54 ` AlexChen
2020-11-16 16:50 ` Thomas Huth
2020-11-17 1:13 ` Alex Chen
2020-11-17 11:35 ` Alex Bennée [this message]
2020-11-17 11:36 ` Thomas Huth
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=87k0ukw70v.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=alex.chen@huawei.com \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.com \
--cc=zhang.zhanghailiang@huawei.com \
--cc=zhengchuan@huawei.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;
as well as URLs for NNTP newsgroup(s).