diff options
| author | Julian Wiedmann <jwi@linux.vnet.ibm.com> | 2018-03-20 07:59:14 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-03-31 18:12:34 +0200 |
| commit | e960fa03f95d68400af2a32808cc43072005ff53 (patch) | |
| tree | 6fff148b778df85f1701cc6ca73c606807cee1bf /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | f9b4ec9fb686daa1d312b16b5bf50a6f760e93b8 (diff) | |
s390/qeth: lock read device while queueing next buffer
[ Upstream commit 17bf8c9b3d499d5168537c98b61eb7a1fcbca6c2 ]
For calling ccw_device_start(), issue_next_read() needs to hold the
device's ccwlock.
This is satisfied for the IRQ handler path (where qeth_irq() gets called
under the ccwlock), but we need explicit locking for the initial call by
the MPC initialization.
Signed-off-by: Julian Wiedmann <jwi@linux.vnet.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions