diff options
| author | Sylwester Nawrocki <[email protected]> | 2012-11-22 11:12:16 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <[email protected]> | 2012-11-26 18:30:19 -0200 |
| commit | ba6b372cf0af564bdc6c14bf68e078ae34bef222 (patch) | |
| tree | b5c2da9fd63da3d145e7a9dd530cb2319a5e576f /tools/perf/util/trace-event-scripting.c | |
| parent | 97d66c47277fc801bc1ee93559a848057181ea55 (diff) | |
[media] s5p-fimc: Don't use mutex_lock_interruptible() in device release()
Use uninterruptible mutex_lock in the release() file op to make
sure all resources are properly freed when a process is being
terminated. Returning -ERESTARTSYS has no effect for a terminating
process and this caused driver resources not to be released. Not
releasing the buffer queue also prevented other drivers to free
memory, e.g. in MMAP -> USERPTR scenario.
This patch is required for stable kernels v3.6+.
Reported-by: Kamil Debski <[email protected]>
Reported-by: Marek Szyprowski <[email protected]>
Signed-off-by: Sylwester Nawrocki <[email protected]>
Signed-off-by: Kyungmin Park <[email protected]>
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions