futex: Plug a pi_state leak and clarify the refcounting
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | futex: Drop refcount if requeue_pi() acquired the rtmutexkernel/ | +5 | 0 replies | |
| 2/5 | futex: Rename free_pi_state() to put_pi_state()kernel/ | +10 | 0 replies | |
| 3/5 | futex: Document pi_state refcounting in requeue codekernel/ | +33 | 1 reply | |
| 4/5 | futex: Remove pointless put_pi_state calls in requeue()kernel/ | +2 | 0 replies | |
| 5/5 | futex: Cleanup the goto confusion in requeue_pi()kernel/ | +3 | 4 replies |
Reviews trailers per patch
1 of 5 patches has a Reviewed-by or Acked-by.
| Patch | Darren Hart |
|---|---|
| 1/5 | |
| 2/5 | |
| 3/5 | |
| 4/5 | |
| 5/5 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [patch 0/5] futex: Plug a pi_state leak and clarify the refcounting
A recent patch claimed that there is a double free in the requeue_pi code, which is not the case.
While analysing the issue I found the contrary, i.e. a leak. This series fixes the leak and clarifies the code so it's more clear how that refcounting on the pi state works.
Thanks,
tglx