From: Denis Kenzior <denkenz at gmail.com>
To: ell at lists.01.org
Subject: Re: [PATCH] dhcp-transport: Do not leak fds during bind
Date: Wed, 18 May 2022 11:22:32 -0500 [thread overview]
Message-ID: <ec5e1008-0298-e17c-7aa7-1a9ca69face1@gmail.com> (raw)
In-Reply-To: 20220516195533.31106-1-denkenz@gmail.com
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
On 5/16/22 14:55, Denis Kenzior wrote:
> When a lease is renewed, the transport bind operation is called. This
> can be done multiple times by dhcp_client, whenever a lease has been
> obtained or renewed. This can result in fds being leaked.
>
> If bind operation has previously succeeded, simply return and reuse the
> already created fd.
> ---
> ell/dhcp-transport.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
Applied.
next reply other threads:[~2022-05-18 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 16:22 Denis Kenzior [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-16 19:55 [PATCH] dhcp-transport: Do not leak fds during bind Denis Kenzior
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=ec5e1008-0298-e17c-7aa7-1a9ca69face1@gmail.com \
--to=ell@lists.linux.dev \
/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