bpf: bpf_iter_task_next: use next_task(kit->task) rather than next_task(kit->pos)
authorOleg Nesterov <oleg@redhat.com>
Tue, 14 Nov 2023 16:32:39 +0000 (17:32 +0100)
committerAlexei Starovoitov <ast@kernel.org>
Sun, 19 Nov 2023 19:43:44 +0000 (11:43 -0800)
commitac8148d957f50434411a0c15a2e4f352b5bb4ff2
tree03207b5d4cbc3593a51decfb3dac6b755636f5b4
parent5a34f9dabd9aa567e2d37e1aa27a67f80acfaa1c
bpf: bpf_iter_task_next: use next_task(kit->task) rather than next_task(kit->pos)

This looks more clear and simplifies the code. While at it, remove the
unnecessary initialization of pos/task at the start of bpf_iter_task_new().

Note that we can even kill kit->task, we can just use pos->group_leader,
but I don't understand the BUILD_BUG_ON() checks in bpf_iter_task_new().

Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Acked-by: Yonghong Song <yonghong.song@linux.dev>
Link: https://lore.kernel.org/r/20231114163239.GA903@redhat.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
kernel/bpf/task_iter.c