6594690b39
When moving from one frontend to another an application could spawn multiple threads opening the same new frontend and in some circumstances all of these could become delayed waiting for the previous frontend readers or previous frontend writer thread to complete. In this scenario the first thread will succeed on open to bring the new frontend online but any others will return EBUSY. This is a fault. If the first succeeds and all others are on the same frontend then they should succeed also. Signed-off-by: Darron Broad <darron@kewl.org> Signed-off-by: Steven Toth <stoth@linuxtv.org> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com> |
||
|---|---|---|
| .. | ||
| b2c2 | ||
| bt8xx | ||
| dm1105 | ||
| dvb-core | ||
| dvb-usb | ||
| frontends | ||
| pluto2 | ||
| siano | ||
| ttpci | ||
| ttusb-budget | ||
| ttusb-dec | ||
| Kconfig | ||
| Makefile | ||