From: Yiyang Chen <cyyzero16@gmail.com>
To: Balbir Singh <balbirs@nvidia.com>,
Yang Yang <yang.yang29@zte.com.cn>,
Wang Yaxin <wang.yaxin@zte.com.cn>
Cc: linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
"Dr . Thomas Orgis" <thomas.orgis@uni-hamburg.de>,
Andrew Morton <akpm@linux-foundation.org>,
stable@vger.kernel.org, Yiyang Chen <cyyzero16@gmail.com>
Subject: [PATCH v3 0/2] taskstats: fix TGID dead-thread stat retention
Date: Mon, 13 Apr 2026 23:45:43 +0800 [thread overview]
Message-ID: <cover.1776094300.git.cyyzero16@gmail.com> (raw)
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
next reply other threads:[~2026-04-13 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 15:45 Yiyang Chen [this message]
2026-04-13 15:45 ` [PATCH v3 1/2] taskstats: retain dead thread stats in TGID queries Yiyang Chen
2026-04-13 15:45 ` [PATCH v3 2/2] selftests/acct: add taskstats TGID retention test Yiyang Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1776094300.git.cyyzero16@gmail.com \
--to=cyyzero16@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=balbirs@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=stable@vger.kernel.org \
--cc=thomas.orgis@uni-hamburg.de \
--cc=wang.yaxin@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox