diff options
| author | Todd Kjos <tkjos@android.com> | 2017-06-29 12:01:53 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-07-17 14:47:30 +0200 |
| commit | d99c7333ab1c9d56e6f6e15c0b4398591465efc1 (patch) | |
| tree | 6b0029f5e7a52579c60916fabd9f5301819d63e9 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | b05a68e94b97eae2ae671ed703416f8dd21e4257 (diff) | |
| download | linux-d99c7333ab1c9d56e6f6e15c0b4398591465efc1.tar.gz linux-d99c7333ab1c9d56e6f6e15c0b4398591465efc1.zip | |
binder: use atomic for transaction_log index
The log->next index for the transaction log was
not protected when incremented. This led to a
case where log->next++ resulted in an index
larger than ARRAY_SIZE(log->entry) and eventually
a bad access to memory.
Fixed by making the log index an atomic64 and
converting to an array by using "% ARRAY_SIZE(log->entry)"
Also added "complete" field to the log entry which is
written last to tell the print code whether the
entry is complete
Signed-off-by: Todd Kjos <tkjos@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions