diff options
| author | Eric Farman <farman@linux.ibm.com> | 2026-07-28 05:30:19 +0200 |
|---|---|---|
| committer | Christian Borntraeger <borntraeger@linux.ibm.com> | 2026-07-30 19:50:31 +0200 |
| commit | 79c60b2c61105368dcc8444eb45847e21734f7c4 (patch) | |
| tree | 6efa50a9e4ba84ee896858d81a31c352720830a0 /tools/perf/scripts/python/bin | |
| parent | 9f5f9a78fedc45bc29d6a0a64e3a3472361afae5 (diff) | |
s390/vfio_ccw: Cancel existing workqueues
The initialization of the io_work and crw_work workqueues begs the
question of whether they should be un-initialized. Add the corresponding
cleanup tags in _release_dev to ensure work isn't dispatched after
the private struct is free'd.
Suggested-by: Matthew Rosato <mjrosato@linux.ibm.com>
Fixes: e5f84dbaea59 ("vfio: ccw: return I/O results asynchronously")
Fixes: 3f02cb2fd9d2 ("vfio-ccw: Wire up the CRW irq and CRW region")
Cc: stable@vger.kernel.org
Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
Signed-off-by: Eric Farman <farman@linux.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@linux.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions