From: Leon Hwang <leon.hwang@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: sashiko-reviews@lists.linux.dev, bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf-next v13 6/8] bpf: Add syscall common attributes support for map_create
Date: Thu, 14 May 2026 21:59:27 +0800 [thread overview]
Message-ID: <7a386625-5793-41eb-a54c-dc3f2aac4ded@linux.dev> (raw)
In-Reply-To: <CAADnVQ+XR3kyqizGgGhtG5xiBu3oK3O+COUMfPDQDBSJbm=56A@mail.gmail.com>
On 2026/5/14 01:02, Alexei Starovoitov wrote:
> On Wed, May 13, 2026 at 3:50 AM Leon Hwang <leon.hwang@linux.dev> wrote:
>>
>> On 13/5/26 07:36, sashiko-bot@kernel.org wrote:
>> [...]
>>>> +
>>>> + err = __map_create(attr, uattr, log);
>>>> +
>>>> + ret = bpf_log_attr_finalize(&attr_log, log);
>>>> + if (ret) {
>>>> + if (err >= 0)
>>>> + close_fd(err);
>>>
>>> Is it safe to call close_fd() here? Since __map_create() uses
>>> bpf_map_new_fd() to allocate and publish the file descriptor via
>>> fd_install(), the file descriptor is already visible to userspace.
>>>
>>
>> I think it is acceptable to close_fd() here, that the duration between
>> fd_install() and close_fd() is short.
>
> bot is correct. Let's avoid these races.
> Pls move bpf_log_attr_finalize() into map_create and do it
> before security_bpf_map_create.
Will do it.
Thanks,
Leon
next prev parent reply other threads:[~2026-05-14 13:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 15:28 [PATCH bpf-next v13 0/8] bpf: Extend BPF syscall with common attributes support Leon Hwang
2026-05-11 15:28 ` [PATCH bpf-next v13 1/8] " Leon Hwang
2026-05-11 16:19 ` bot+bpf-ci
2026-05-11 16:53 ` Alexei Starovoitov
2026-05-12 2:41 ` Leon Hwang
2026-05-11 15:28 ` [PATCH bpf-next v13 2/8] libbpf: Add support for extended BPF syscall Leon Hwang
2026-05-11 15:28 ` [PATCH bpf-next v13 3/8] bpf: Refactor reporting log_true_size for prog_load Leon Hwang
2026-05-11 15:28 ` [PATCH bpf-next v13 4/8] bpf: Add syscall common attributes support " Leon Hwang
2026-05-12 22:18 ` sashiko-bot
2026-05-13 10:44 ` Leon Hwang
2026-05-11 15:28 ` [PATCH bpf-next v13 5/8] bpf: Add syscall common attributes support for btf_load Leon Hwang
2026-05-11 15:28 ` [PATCH bpf-next v13 6/8] bpf: Add syscall common attributes support for map_create Leon Hwang
2026-05-11 16:19 ` bot+bpf-ci
2026-05-11 17:07 ` Alexei Starovoitov
2026-05-12 2:47 ` Leon Hwang
2026-05-12 23:36 ` sashiko-bot
2026-05-13 10:45 ` Leon Hwang
2026-05-13 17:02 ` Alexei Starovoitov
2026-05-14 13:59 ` Leon Hwang [this message]
2026-05-11 15:28 ` [PATCH bpf-next v13 7/8] libbpf: " Leon Hwang
2026-05-12 23:56 ` sashiko-bot
2026-05-13 10:46 ` Leon Hwang
2026-05-11 15:28 ` [PATCH bpf-next v13 8/8] selftests/bpf: Add tests to verify map create failure log Leon Hwang
2026-05-13 0:33 ` sashiko-bot
2026-05-13 10:47 ` Leon Hwang
2026-05-13 16:58 ` Alexei Starovoitov
2026-05-14 13:59 ` Leon Hwang
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=7a386625-5793-41eb-a54c-dc3f2aac4ded@linux.dev \
--to=leon.hwang@linux.dev \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=sashiko-reviews@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 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.