From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev,
alexei.starovoitov@gmail.com, andrii@kernel.org, song@kernel.org,
haoluo@google.com, yonghong.song@linux.dev, daniel@iogearbox.net,
kpsingh@kernel.org, sdf@google.com, jolsa@kernel.org,
john.fastabend@gmail.com, hsinweih@uci.edu, houtao1@huawei.com
Subject: Re: [PATCH bpf-next v3] bpf: Check map->usercnt after timer->timer is assigned
Date: Thu, 02 Nov 2023 06:00:24 +0000 [thread overview]
Message-ID: <169890482495.9002.6880714745373814049.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231030063616.1653024-1-houtao@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 30 Oct 2023 14:36:16 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> When there are concurrent uref release and bpf timer init operations,
> the following sequence diagram is possible. It will break the guarantee
> provided by bpf_timer: bpf_timer will still be alive after userspace
> application releases or unpins the map. It also will lead to kmemleak
> for old kernel version which doesn't release bpf_timer when map is
> released.
>
> [...]
Here is the summary with links:
- [bpf-next,v3] bpf: Check map->usercnt after timer->timer is assigned
https://git.kernel.org/bpf/bpf/c/fd381ce60a2d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-11-02 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 6:36 [PATCH bpf-next v3] bpf: Check map->usercnt after timer->timer is assigned Hou Tao
2023-11-02 6:00 ` patchwork-bot+netdevbpf [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=169890482495.9002.6880714745373814049.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=hsinweih@uci.edu \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yonghong.song@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