This series fixes a taskstats TGID aggregation bug where fields added in
the TGID query path were not preserved after thread exit, and adds a
kselftest covering the regression.

The first patch keeps the cached TGID aggregate used for dead threads in
step with the fields already accumulated for live threads, and also fixes
the final TGID exit notification emitted when group_dead is true.

The second patch adds a kselftest that verifies TGID CPU stats do not
regress after a worker thread exits and has been reaped.

---

Changes in v3:
- fix the helper comment in patch 1 to use per-task-foo(stats, tsk)
- add Acked-by tags to both patches
- Link to v2: <https://lore.kernel.org/all/cover.1776020234.git.cyyzero16@gmail.com/>

Changes in v2:
- add Fixes tags for the two commits that introduced the regression
- clarify that the regression affects both TGID queries and the final
  TGID exit notification
- add a kselftest that checks TGID CPU stats do not regress after
  thread exit
- Link to v1: <https://lore.kernel.org/all/6f4ed79d96c389a9a1d67d5ced96c6326eda82ae.1774552296.git.cyyzero16@gmail.com/>

-- 
2.43.0

Hi Andrew,

Just a gentle ping on this taskstats fix series [1], which fixes a TGID
aggregation bug and adds a kselftest.

The series already has an Ack from Balbir [2], so I wanted to check if
there’s anything else needed from my side, or if it looks suitable for
you to pick up into nonmm-unstable?

Thanks,
Yiyang

[1] https://lore.kernel.org/all/cover.1776094300.git.cyyzero16@gmail.com/
[2] https://lore.kernel.org/all/d530ffd7-ebfa-46e1-afd3-2599a3ffaa55@nvidia.com/