introduce __next_thread(), change next_thread()
Status from this message: [merged mm-nonmm-stable] change-next_thread-to-use-__next_thread-group_leader.patch removed from -mm tree
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 All 2 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | introduce __next_thread(), fix next_tid() vs exec() racefs/ include/ | +13 | 0 replies | Applied |
| 2/2 | change next_thread() to use __next_thread() ?: group_leaderinclude/ | +2 | 0 replies | Applied |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] introduce __next_thread(), change next_thread()
Hello,
After document-while_each_thread-change-first_tid-to-use-for_each_thread.patch in mm tree + this series
1. We have only one lockless user of next_thread(), task_group_seq_get_next(). I think it should be changed too.
2. We have only one user of task_struct->thread_group, thread_group_empty(). The next patches will change thread_group_empty() and kill ->thread_group.
Oleg.