From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, sdf@google.com,
martin.lau@linux.dev, andrii@kernel.org, song@kernel.org,
haoluo@google.com, yhs@fb.com, daniel@iogearbox.net,
kpsingh@kernel.org, jolsa@kernel.org, john.fastabend@gmail.com,
houtao1@huawei.com
Subject: Re: [PATCH bpf v2 0/2] Wait for busy refill_work when destroying bpf memory allocator
Date: Sat, 22 Oct 2022 02:30:18 +0000 [thread overview]
Message-ID: <166640581830.9082.444322122307473295.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221021114913.60508-1-houtao@huaweicloud.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 21 Oct 2022 19:49:11 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> Hi,
>
> The patchset aims to fix one problem of bpf memory allocator destruction
> when there is PREEMPT_RT kernel or kernel with arch_irq_work_has_interrupt()
> being false (e.g. 1-cpu arm32 host or mips). The root cause is that
> there may be busy refill_work when the allocator is destroying and it
> may incur oops or other problems as shown in patch #1. Patch #1 fixes
> the problem by waiting for the completion of irq work during destroying
> and patch #2 is just a clean-up patch based on patch #1. Please see
> individual patches for more details.
>
> [...]
Here is the summary with links:
- [bpf,v2,1/2] bpf: Wait for busy refill_work when destroying bpf memory allocator
https://git.kernel.org/bpf/bpf/c/3d05818707bb
- [bpf,v2,2/2] bpf: Use __llist_del_all() whenever possbile during memory draining
https://git.kernel.org/bpf/bpf/c/fa4447cb73b2
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:[~2022-10-22 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 11:49 [PATCH bpf v2 0/2] Wait for busy refill_work when destroying bpf memory allocator Hou Tao
2022-10-21 11:49 ` [PATCH bpf v2 1/2] bpf: " Hou Tao
2022-10-21 11:49 ` [PATCH bpf v2 2/2] bpf: Use __llist_del_all() whenever possbile during memory draining Hou Tao
2022-10-22 2: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=166640581830.9082.444322122307473295.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=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--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=yhs@fb.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.