prepare for ->siglock safe threads traversal
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 of 4 patches 4 repliesIn review
2 of 4 patches are in this archive. The cover letter announces 4.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 3/4 | cleanup __exit_signal()kernel/ | +15 | 3 replies | |
| 4/4 | rename __exit_sighand to cleanup_sighandinclude/ kernel/ kernel/ | +14 | 1 reply |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | [email protected] |
|---|---|
| 3/4 | A-b |
| 4/4 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/4] prepare for ->siglock safe threads traversal
The main problem is that copy_process's error path and release_task() share __exit_signal() which locks ->sighand and destroys it, but we need to do __unhash_process() under ->sighand.
This patch series tries to solves this. It also tries to simplify and cleanup the code a bit.
Oleg.