aboutsummaryrefslogtreecommitdiffstats
path: root/crypto/async_tx/raid6test.c
diff options
context:
space:
mode:
authorStephan Gatzka <stephan.gatzka@gmail.com>2013-08-26 20:50:05 +0200
committerStefan Richter <stefanr@s5r6.in-berlin.de>2013-08-29 22:35:05 +0200
commitdb9ae8fec7b19f0ac6c60d998cac968d801a998d (patch)
treeb8042b322264f0be3539e37a254f4f1f06b06e03 /crypto/async_tx/raid6test.c
parent7a723c6ed9e92bf91db5c65542c78106030afdbe (diff)
downloadkernel_goldelico_gta04-db9ae8fec7b19f0ac6c60d998cac968d801a998d.zip
kernel_goldelico_gta04-db9ae8fec7b19f0ac6c60d998cac968d801a998d.tar.gz
kernel_goldelico_gta04-db9ae8fec7b19f0ac6c60d998cac968d801a998d.tar.bz2
firewire: ohci: Fix deadlock at bus reset
Put bus_reset_work into its own workqueue. By doing this, forward progress of bus_reset_work() is guaranteed if the work is switched over to a rescuer thread. Switching work to a rescuer thread happens if a new worker thread could not be allocated in certain time (MAYDAY_INITIAL_TIMEOUT, typically 10 ms). This might not be possible under high memory pressure or even on a heavily loaded embedded system running a slow serial console. The former deadlock occured in the following situation: The rescuer thread ran fw_device_init->read_config_rom->read_rom->fw_run_transaction. fw_run_transaction blocked waiting for the completion object. This completion object would have been completed in bus_reset_work, but this work was never executed in the rescuer thread due to its strictly sequential behaviour. [Stefan R.: Removed WQ_NON_REENTRANT flag from allocation because it is no longer needed in current kernels. Add it back if you backport to kernels older than 3.7, i.e. one which does not contain dbf2576e37da "workqueue: make all workqueues non-reentrant". Swapped order of destroy_workqueue and pci_unregister_driver.] Signed-off-by: Stephan Gatzka <stephan.gatzka@gmail.com> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Diffstat (limited to 'crypto/async_tx/raid6test.c')
0 files changed, 0 insertions, 0 deletions