diff options
| author | Hans de Goede <[email protected]> | 2022-10-23 21:13:01 +0100 |
|---|---|---|
| committer | Mauro Carvalho Chehab <[email protected]> | 2022-11-25 08:18:44 +0000 |
| commit | 36c953e1efa8249fb2d85a1f396d885a9463e9a8 (patch) | |
| tree | c7fdb5627a99bbcb9cf0c93e01bb7f33cf7f1ed3 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | afbfe82cbba3aab816ef3b8bf13450bba7c25cad (diff) | |
media: atomisp: Flush queue on atomisp_css_start() error
I managed to trigger an atomisp_css_start() error by pushing my test system
towards an OOM situation, this triggered the following WARN_ON() in
__vb2_queue_cancel() in videobuf2-core.c:
/*
* If you see this warning, then the driver isn't cleaning up properly
* after a failed start_streaming(). See the start_streaming()
* documentation in videobuf2-core.h for more information how buffers
* should be returned to vb2 in start_streaming().
*/
if (WARN_ON(atomic_read(&q->owned_by_drv_count))) {
Fix this by calling atomisp_flush_video_pipe() to return any queued buffers
back to the videobuf2-core on an atomisp_css_start() error.
Reviewed-by: Andy Shevchenko <[email protected]>
Signed-off-by: Hans de Goede <[email protected]>
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions