From: patchwork-bot+netdevbpf@kernel.org
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@kernel.org, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, dohyunkim@google.com,
neelnatu@google.com, brho@google.com, htejun@gmail.com,
void@manifault.com
Subject: Re: [PATCH bpf v1 0/3] Fixes for BPF timer lockup and UAF
Date: Wed, 10 Jul 2024 23:30:33 +0000 [thread overview]
Message-ID: <172065423350.5820.8139357490858247646.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240709185440.1104957-1-memxor@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 9 Jul 2024 18:54:37 +0000 you wrote:
> The following patches contain fixes for timer lockups and a
> use-after-free scenario.
>
> This set proposes to fix the following lockup situation for BPF timers.
>
> CPU 1 CPU 2
>
> [...]
Here is the summary with links:
- [bpf,v1,1/3] bpf: Fail bpf_timer_cancel when callback is being cancelled
https://git.kernel.org/bpf/bpf/c/d4523831f07a
- [bpf,v1,2/3] bpf: Defer work in bpf_timer_cancel_and_free
https://git.kernel.org/bpf/bpf/c/a6fcd19d7eac
- [bpf,v1,3/3] selftests/bpf: Add timer lockup selftest
(no matching commit)
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:[~2024-07-10 23:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 18:54 [PATCH bpf v1 0/3] Fixes for BPF timer lockup and UAF Kumar Kartikeya Dwivedi
2024-07-09 18:54 ` [PATCH bpf v1 1/3] bpf: Fail bpf_timer_cancel when callback is being cancelled Kumar Kartikeya Dwivedi
2024-07-09 18:54 ` [PATCH bpf v1 2/3] bpf: Defer work in bpf_timer_cancel_and_free Kumar Kartikeya Dwivedi
2024-07-09 18:54 ` [PATCH bpf v1 3/3] selftests/bpf: Add timer lockup selftest Kumar Kartikeya Dwivedi
2024-07-09 21:06 ` Kumar Kartikeya Dwivedi
2024-07-10 23:28 ` Alexei Starovoitov
2024-07-11 2:56 ` Kumar Kartikeya Dwivedi
2024-07-10 23:30 ` 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=172065423350.5820.8139357490858247646.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=brho@google.com \
--cc=daniel@iogearbox.net \
--cc=dohyunkim@google.com \
--cc=eddyz87@gmail.com \
--cc=htejun@gmail.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=neelnatu@google.com \
--cc=song@kernel.org \
--cc=void@manifault.com \
--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