diff options
author | Eric Farman <[email protected]> | 2021-05-11 21:56:29 +0200 |
---|---|---|
committer | Cornelia Huck <[email protected]> | 2021-05-12 12:59:50 +0200 |
commit | c6c82e0cd8125d30f2f1b29205c7e1a2f1a6785b (patch) | |
tree | c2a1ef68f6f2d6d427d0c798c1ec711fe6a34412 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 6efb943b8616ec53a5e444193dccf1af9ad627b5 (diff) |
vfio-ccw: Check initialized flag in cp_init()
We have a really nice flag in the channel_program struct that
indicates if it had been initialized by cp_init(), and use it
as a guard in the other cp accessor routines, but not for a
duplicate call into cp_init(). The possibility of this occurring
is low, because that flow is protected by the private->io_mutex
and FSM CP_PROCESSING state. But then why bother checking it
in (for example) cp_prefetch() then?
Let's just be consistent and check for that in cp_init() too.
Fixes: 71189f263f8a3 ("vfio-ccw: make it safe to access channel programs")
Signed-off-by: Eric Farman <[email protected]>
Reviewed-by: Cornelia Huck <[email protected]>
Acked-by: Matthew Rosato <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Cornelia Huck <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions