copy_process/attach_pid minor fix + cleanups
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest4 patches 1 replyIn review
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | de_thread: use change_pid() rather than detach_pid/attach_pidfs/ | +1 | 1 reply | |
| 2/4 | copy_process: unify CLONE_THREAD-or-thread_group_leader codekernel/ | +7 | 0 replies | |
| 3/4 | copy_process: don't add the uninitialized child to thread/task/pid listsinclude/ kernel/ kernel/ | +19 | 0 replies | |
| 4/4 | copy_process: consolidate the lockless CLONE_THREAD checkskernel/ | +16 | 0 replies |
Reviews trailers per patch
1 of 4 patches has a Reviewed-by or Acked-by.
| Patch | Eric W. Biederman |
|---|---|
| 1/4 | R-b |
| 2/4 | |
| 3/4 | |
| 4/4 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v2 0/4] copy_process/attach_pid minor fix + cleanups
Hello.
1/4 and 2/4 look like the obvious cleanups.
3/4 tries to fix the minor problem. I have to admit, initially I thought that this problem is more serious. But it seems that nothing really bad can happen if the new task has the wrong pid or group_leader. Still I think this makes sense.
4/4 is offtopic minor cleanup.
This is also another preparation for while_each_thread() fixes.
Oleg.