All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Martin Kelly <martin.kelly@crowdstrike.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
	marco.vedovati@crowdstrike.com
Subject: Re: [PATCH bpf-next] libbpf: set close-on-exec flag on gzopen
Date: Mon, 14 Aug 2023 15:40:22 +0000	[thread overview]
Message-ID: <169202762261.28565.7854580464689609130.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230810214350.106301-1-martin.kelly@crowdstrike.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Thu, 10 Aug 2023 14:43:53 -0700 you wrote:
> From: Marco Vedovati <marco.vedovati@crowdstrike.com>
> 
> Enable the close-on-exec flag when using gzopen
> 
> This is especially important for multithreaded programs making use of
> libbpf, where a fork + exec could race with libbpf library calls,
> potentially resulting in a file descriptor leaked to the new process.
> 
> [...]

Here is the summary with links:
  - [bpf-next] libbpf: set close-on-exec flag on gzopen
    https://git.kernel.org/bpf/bpf-next/c/8e50750f122e

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2023-08-14 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 21:43 [PATCH bpf-next] libbpf: set close-on-exec flag on gzopen Martin Kelly
2023-08-10 22:18 ` Martin Kelly
2023-08-14 17:03   ` Stanislav Fomichev
2023-08-14 18:48     ` [External] " Martin Kelly
2023-08-14 15:40 ` patchwork-bot+netdevbpf [this message]
2023-08-14 15:40 ` Daniel Borkmann
2023-08-14 19:22   ` Martin Kelly

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=169202762261.28565.7854580464689609130.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=marco.vedovati@crowdstrike.com \
    --cc=martin.kelly@crowdstrike.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.