| Message ID | 20230905154612.GA24872@redhat.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | bpf: task_group_seq_get_next: misc cleanups | expand |
sorry for noise, forgot to mention... this (hopefully simple) series was only compile-tested. On 09/05, Oleg Nesterov wrote: > > Yonghong, > > I am resending 1-5 of 6 as you suggested with your acks included. > > The next (final) patch will change this code to use __next_thread when > > https://lore.kernel.org/all/20230824143142.GA31222@redhat.com/ > > is merged. > > Oleg.
On Tue, Sep 5, 2023 at 12:59 PM Oleg Nesterov <oleg@redhat.com> wrote: > > sorry for noise, forgot to mention... > > this (hopefully simple) series was only compile-tested. > > On 09/05, Oleg Nesterov wrote: > > > > Yonghong, > > > > I am resending 1-5 of 6 as you suggested with your acks included. > > > > The next (final) patch will change this code to use __next_thread when > > > > https://lore.kernel.org/all/20230824143142.GA31222@redhat.com/ > > > > is merged. The patch set looks fine. What is the next step? Should we merge it now in bpf-next and then during the next merge window you'll follow up with __next_thread clean up?
On 09/06, Alexei Starovoitov wrote: > > On Tue, Sep 5, 2023 at 12:59 PM Oleg Nesterov <oleg@redhat.com> wrote: > > > > > The next (final) patch will change this code to use __next_thread when > > > > > > https://lore.kernel.org/all/20230824143142.GA31222@redhat.com/ > > > > > > is merged. > > The patch set looks fine. > What is the next step? > Should we merge it now in bpf-next and then during the next merge window > you'll follow up with __next_thread clean up? Thanks, works for me. Oleg.
Hello: This series was applied to bpf/bpf-next.git (master) by Alexei Starovoitov <ast@kernel.org>: On Tue, 5 Sep 2023 17:46:12 +0200 you wrote: > Yonghong, > > I am resending 1-5 of 6 as you suggested with your acks included. > > The next (final) patch will change this code to use __next_thread when > > https://lore.kernel.org/all/20230824143142.GA31222@redhat.com/ > > [...] Here is the summary with links: - [bpf-next,v2,1/5] bpf: task_group_seq_get_next: cleanup the usage of next_thread() https://git.kernel.org/bpf/bpf-next/c/f9aedd66c46b - [bpf-next,v2,2/5] bpf: task_group_seq_get_next: cleanup the usage of get/put_task_struct https://git.kernel.org/bpf/bpf-next/c/ad98e2e5f84f - [bpf-next,v2,3/5] bpf: task_group_seq_get_next: fix the skip_if_dup_files check https://git.kernel.org/bpf/bpf-next/c/c12e785e8648 - [bpf-next,v2,4/5] bpf: task_group_seq_get_next: kill next_task https://git.kernel.org/bpf/bpf-next/c/c40a3b44f7c5 - [bpf-next,v2,5/5] bpf: task_group_seq_get_next: simplify the "next tid" logic https://git.kernel.org/bpf/bpf-next/c/1e48f069c90f You are awesome, thank you!