diff options
| author | Chengming Zhou <[email protected]> | 2022-02-20 13:14:24 +0800 |
|---|---|---|
| committer | Peter Zijlstra <[email protected]> | 2022-03-01 16:18:37 +0100 |
| commit | 248cc9993d1cc12b8e9ed716cc3fc09f6c3517dd (patch) | |
| tree | e97bb003738542a43b72421b2f88737f26a62b92 /lib/test_fortify/write_overflow-strlcpy-src.c | |
| parent | 6255b48aebfd4dff375e97fc8b075a235848db0b (diff) | |
sched/cpuacct: Fix charge percpu cpuusage
The cpuacct_account_field() is always called by the current task
itself, so it's ok to use __this_cpu_add() to charge the tick time.
But cpuacct_charge() maybe called by update_curr() in load_balance()
on a random CPU, different from the CPU on which the task is running.
So __this_cpu_add() will charge that cputime to a random incorrect CPU.
Fixes: 73e6aafd9ea8 ("sched/cpuacct: Simplify the cpuacct code")
Reported-by: Minye Zhu <[email protected]>
Signed-off-by: Chengming Zhou <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Acked-by: Tejun Heo <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'lib/test_fortify/write_overflow-strlcpy-src.c')
0 files changed, 0 insertions, 0 deletions