diff options
| author | SJLIN0 <[email protected]> | 2022-09-15 09:28:00 +0800 |
|---|---|---|
| committer | Mark Brown <[email protected]> | 2022-09-19 18:35:23 +0100 |
| commit | 7042bde216ada135b2f88423ae714ab9a22e3a22 (patch) | |
| tree | e95b169369d21c6acd0ff935d0735ff1a6ae3c73 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | 4a13c949501902d4e6b59cc693005f4ca352dc15 (diff) | |
ASoC: nau8824: Fix semaphore is released unexpectedly
On resuming, we anticipate that the jack is detected before playback
or capture. Therefore, we use semaphore to control the jack detection
done without any bothering. During booting, the driver launches jack
detection and releases the semaphore. However, it doesn't perceive the
maniputation of semaphore is not like resuming procedure. This makes
the semaphore's count value become to 2. There is more than one thread
can enter into the critical section. This may get unexpected situation
and make some chaos.
Signed-off-by: SJLIN0 <[email protected]>
Signed-off-by: Wallace Lin <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Mark Brown <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions