diff options
author | NeilBrown <[email protected]> | 2017-04-07 10:03:26 +1000 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2017-04-11 09:06:32 +0200 |
commit | 717a94b5fc7092afebe9c93791f29b2d8e5d297a (patch) | |
tree | 9a7c56b8c2daac8ea7c0f39f58e4c5aa84615ad3 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 36a4dfc37856cae40e4d864950f768d8b7d4f9f5 (diff) |
sched/core: Remove 'task' parameter and rename tsk_restore_flags() to current_restore_flags()
It is not safe for one thread to modify the ->flags
of another thread as there is no locking that can protect
the update.
So tsk_restore_flags(), which takes a task pointer and modifies
the flags, is an invitation to do the wrong thing.
All current users pass "current" as the task, so no developers have
accepted that invitation. It would be best to ensure it remains
that way.
So rename tsk_restore_flags() to current_restore_flags() and don't
pass in a task_struct pointer. Always operate on current->flags.
Signed-off-by: NeilBrown <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Mel Gorman <[email protected]>
Cc: Michal Hocko <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: [email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions