diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2020-07-16 16:48:47 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2020-07-16 16:48:47 -0700 |
| commit | 4291dc1a5608117439643f4fe77e4ad1827a3310 (patch) | |
| tree | 4a873e972e1bcde088a7204b4511299ddcbf04fd /drivers/net/phy/phy_device.c | |
| parent | 89e35f66d552c98c1cfee4a058de158d7f21796a (diff) | |
| parent | ac5c66f261b7174d0d9aaeb2bf9f8c2c2dbad0bd (diff) | |
Merge branch 'net-sched-do-not-drop-root-lock-in-tcf_qevent_handle'
Petr Machata says:
====================
net: sched: Do not drop root lock in tcf_qevent_handle()
Mirred currently does not mix well with blocks executed after the qdisc
root lock is taken. This includes classification blocks (such as in PRIO,
ETS, DRR qdiscs) and qevents. The locking caused by the packet mirrored by
mirred can cause deadlocks: either when the thread of execution attempts to
take the lock a second time, or when two threads end up waiting on each
other's locks.
The qevent patchset attempted to not introduce further badness of this
sort, and dropped the lock before executing the qevent block. However this
lead to too little locking and races between qdisc configuration and packet
enqueue in the RED qdisc.
Before the deadlock issues are solved in a way that can be applied across
many qdiscs reasonably easily, do for qevents what is done for the
classification blocks and just keep holding the root lock.
That is done in patch #1. Patch #2 then drops the now unnecessary root_lock
argument from Qdisc_ops.enqueue.
====================
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'drivers/net/phy/phy_device.c')
0 files changed, 0 insertions, 0 deletions