diff options
| author | Prashanth Bhatta <bhattap@codeaurora.org> | 2016-08-20 20:02:45 -0700 |
|---|---|---|
| committer | Gerrit - the friendly Code Review server <code-review@localhost> | 2016-08-27 12:09:16 -0700 |
| commit | 7d45313e05f7de3f210c09e40da5b438e397d880 (patch) | |
| tree | 24821536c7d4bb4326550a18439915d7e5ebc4eb /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | e8a0e0808d1862467d32aaee8982b5b6500ba89c (diff) | |
icnss: Handle wait being interrupted
When event needs to be processed synchronously, event posting
thread waits for the completion. After completion, result from
the event work is retrieved and event buffer would be freed. But
if waiting thread gets interrupted then wait_for_completion API
returns failure and it also frees the buffer posted for
processing. Event work queue may accesses the freed buffer and
crash the system.
Fix the issue by properly synchronizing event buffer free between
caller and event work by checking for return value of
wait_for_completion.
CRs-fixed: 1057180
Change-Id: Ic3968fd4c0232da6bc9a97d94376f540f62bd2e6
Signed-off-by: Prashanth Bhatta <bhattap@codeaurora.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions
